attachment
<div dir="ltr"><div><div><div><div><div><div>Hi Randy,<br><br></div><div>Yes, we agreed to add a TTL to the registration (consistent w/ notification subscriptions,<br></div><div>etc.).<br><br></div>The Device-Keep-Alive operation was renamed Get-Notifications (to align w/ IPP).<br>
</div>The notifications *are* asynchronous from the Cloud Imaging Service to the Proxy<br></div>(keep-alive, jobs-available, etc.). The in-band IPP Get-Notifications mapping saves<br></div>introducing XMPP or some other notification transport.<br>
<br></div><div>Cheers,<br></div><div>- Ira<br><br></div><div><br></div>Cheers,<br></div>- Ira<br></div><div class="gmail_extra"><br clear="all"><div>Ira McDonald (Musician / Software Architect)<br>Chair - Linux Foundation Open Printing WG<br>
Secretary - IEEE-ISTO Printer Working Group<br>Co-Chair - IEEE-ISTO PWG IPP WG<br>Co-Chair - TCG Trusted Mobility Solutions WG<br>Chair - TCG Embedded Systems Hardcopy SG<br>IETF Designated Expert - IPP & Printer MIB<br>
Blue Roof Music/High North Inc<br><a style="color:rgb(51,51,255)" href="http://sites.google.com/site/blueroofmusic" target="_blank">http://sites.google.com/site/blueroofmusic</a><br><a style="color:rgb(102,0,204)" href="http://sites.google.com/site/highnorthinc" target="_blank">http://sites.google.com/site/highnorthinc</a><br>
mailto:<a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>Winter 579 Park Place Saline, MI 48176 734-944-0094<br>Summer PO Box 221 Grand Marais, MI 49839 906-494-2434<br><br><div style="display:inline">
</div><div style="display:inline"></div><div style="display:inline"></div><div></div><div></div><div></div><div></div></div>
<br><br><div class="gmail_quote">On Mon, Sep 30, 2013 at 7:24 PM, Randy Turner <span dir="ltr"><<a href="mailto:rturner@amalfisystems.com" target="_blank">rturner@amalfisystems.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Hi All,<br>
<br>
>From today's conference call, I noticed there was a discussion regarding registration lifetimes -- the cloud service would be the potential bottleneck for scalability, so it might be a good idea for<br>
a "registration-response" to include a time-to-live (TTL) value. This TTL value would indicate to the device when the registration will expire (from the perspective of the cloud service). The device would have to re-register before the TTL expires<br>
<br>
This re-registration *could* be used to obviate the need for an application-layer keep alive.<br>
<br>
<br>
I was curious if the notifications that were discussed were meant to be "asynchronous" -- meaning, the cloud would asynchronously notify a device or client regarding "something" happening in the cloud.<br>
<br>
<br>
R.<br>
<br>
_______________________________________________<br>
cloud mailing list<br>
<a href="mailto:cloud@pwg.org">cloud@pwg.org</a><br>
<a href="https://www.pwg.org/mailman/listinfo/cloud" target="_blank">https://www.pwg.org/mailman/listinfo/cloud</a><br>
</blockquote></div><br></div>