Having discontinuous streams with Jabber, especially over other sockets, is not an impossibility with Jabber protocol-wise (probably do something like send a </stream:stream> but not send presence unavailable beforehand... unless you do want to appear offline for that brief amount of time), it's simply a matter of figuring out exactly how it should be done (ensuring authentication is proper without logging in yet again) and getting servers to support it. I don't think many people would be against the idea if someone figures out a good way to do it. Julian -- email: [EMAIL PROTECTED] jabber:[EMAIL PROTECTED] On 16 Jul 2001 14:40:36 -0700, O'Brien-Strain, Eamonn wrote: > Hello, > > I am looking at the issues involved with putting a Jabber client on wireless > devices. One of the real-world features of such devices is that network > connectivity tends to be intermittent with frequent, sometimes brief, > outages. It seems therefore that the normal Jabber implementation with a > continuously open TCP socket for the duration of a session is a bit > problematic. > > What is the current status of alternate lower layers for Jabber? I have > seen mentions of HTTP but does it mean HTTP as a layer in the network > protocol or does it means implementing a Jabber client in a Web server > allowing the use of a standard web browser as the UI? How about using UDP > instead of TCP sockets? In the XML data being passed back and forth is > there enough information to keep track of session information in the absence > of a continuous connection? > > In general is anyone looking at Jabber on wireless devices? > > Thanks. > __ > Eamonn O'Brien-Strain > HP Labs > [EMAIL PROTECTED] _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
