[Standards] s2s and gracelessly broken streams

[Dave Cridland]

On Wed Apr  4 21:00:44 2007, Matthias Wimmer wrote:
> Hi JD!
> 
> JD Conley schrieb:
> > Yeah. I pointed that out. :) However, there are many cases where
> > bi-directional communication is not necessary. Let's say I walk 
> away
> > from my desktop computer and lock it, or my screensaver goes on. 
> There's
> > a very high probability I'm not going to care about incoming 
> data. The
> > server could just queue that up for me until I come back and my 
> client
> > (now a tad bit smarter) reconnect and re-establishes my session. 
> There
> > are certainly some edges that would need to be worked out (disco, 
> etc).
> 
> I also think of a use-case where the client could tell the server: 
> if
> the connection to gets lost, don't close my session immediatelly but
> wait x seconds for me to get back and queue incoming data for me in 
> the
> meantime. This might be a good thing for mobile clients, that can 
> get
> out of coverage for some seconds/minutes and that will resume the
> session if they get coverage again.

Again, XEP-0198 ought to handle this case - there's no explicit 
negotiation of how long the client might be out of coverage, though - 
does this need to be there?

Dave.
-- 
Dave Cridland - mailto:dave at cridland.net - xmpp:dwd at jabber.org
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade