[standards-jig] Re: thoughts on POP3 Offline (JEP-0013)

Richard Dobson richard at dobson-i.net
Wed Nov 13 19:19:05 UTC 2002


The problem with this is that the <x xmlns='xmpp:x:omm'/> will be
broadcasted inside your presence to everyone in your roster, IMO an IQ based
command is much more appropriate and will also allow the client to find out
if offline messaging is supported at all by seeing if an error response is
generated.

Richard

----- Original Message -----
>From: "Jean-Louis Seguineau/EXC/TEC" <jean-louis.seguineau at antepo.com>
To: <standards-jig at jabber.org>
Sent: Wednesday, November 13, 2002 5:52 PM
Subject: [standards-jig] Re: thoughts on POP3 Offline (JEP-0013)


> Peter,
>
> I do not totally aggree with your statement quote:
> >    Without the ability to query a given client for feature sets,
> >    POP3-like offline message handling is incompatible with the
> >    existing offline model.
>
> We have implemented a very simple model that allow both offline message
> handling to work together without resorting to the full feature
negitiation>
> The offline message retrieval is triggered by the initial presence a
client
> is sending to the server. If you ad an extension to the presence message,
> then the client has a way to advertise its support for a given namespace.
> The client sends the following snippet (this is an extract of our
> implementation of the offline management, hence the different namspace,
but
> it can easily be converted):
>
> <presence>
>
> <show>Chat</show>
>
> <status>Here I am again.</status>
>
> <x xmlns='xmpp:x:omm'/>
>
>         </presence>
>
> and the server is answering with an headline message such as
>
> <message type='headline' to='user at domain'>
>
> <subject>Offline messages</subject>
>
> <body>You have 4 offline messages waiting</body>
>
> <x xmlns='xmpp:x:omm'>
>
> <item jid='contact1 at domain' count='3'/>
>
> <item jid='contact2 at domain'/>
>
> </x>
>
>           </message>
>
> from then on you are back to using the normal iq to handle the rest of the
> dialog. This is a generic solution that allow to catter for offline
> managemet aware client and the old generation.




More information about the Standards mailing list