Eamonn,
I've looked into an HTTP transport and concluded then "simplest" method is
to have a persistent program on a server (such as a servlet) which takes
requests from clients and sends them over a socket it keeps open.
Not plesant, but it'll work.
Al.
----- Original Message -----
From: "O'Brien-Strain, Eamonn" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, July 16, 2001 10:40 PM
Subject: [JDEV] Using HTTP or other connectionless layer for wireless
clients
> 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
_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
