[standards-jig] NEW: Message Delivery Semantics (JEP-0079)

Matthew A. Miller linuxwolf at outer-planes.no-ip.com
Wed Apr 16 15:30:18 UTC 2003

<rule condition="expire-in" value="0" action="drop"/> should handle the
situation you describe perfectly.  The argument you seem to be raising
against this is the case of clients understanding these semantics in a
recipient role.  Bluntly put, the implementing server *MUST NOT* make
any assumptions of this type (and I can add language that explicitly
states this).

If the server cannot deliver such a semantically-marked message
immediately (which depends on how a server interprets "immediately"), it
*MUST NOT* get stored offline (as I thought the JEP clearly outlined). 
The blurb about clients possibly understanding this JEP is a matter of
convenience and consistency for users, but (again) servers MUST NOT make
the assumption that the client can deal with it.

Put another way, if a server does not discard or deliver a "this message
expires in X number of milliseconds" message in that X number of
milliseconds, then it would not be considered to comply with this JEP.

-  LW

On Wed, 2003-04-16 at 05:02, Richard Dobson wrote:
> Sorry but if you think about it and clients follow the suggestion about
> processing the delivery semantics too expires-in of 0 would not really work
> as strictly it will be dropped straight away.
> Richard
> ----- Original Message -----
> From: "Rachel Blackman" <rcb at ceruleanstudios.com>
> To: <standards-jig at jabber.org>
> Sent: Wednesday, April 16, 2003 10:31 AM
> Subject: Re: [standards-jig] NEW: Message Delivery Semantics (JEP-0079)
> > Looks good, but I would also like to see a condition that stops a message
> > from being stored offline at all, as I dont think expires could be used if
> > clients are also processing this as say a expires-in of 0 would possibly
> > be dropped by the server or the client when it receives it as it might
> > have taken a little while to arrive.
> Actually, I think expires-in works perfectly for this, provided it's
> handled by the final destination server.  (Which I think needs to be the
> behavior anyway.)  If the server I am on receives a message with an
> expires-in of 0 for me, and I am online, it should pass it on to me
> immediately; from the point of view of the server (since expires-in is
> counted from message reception), there's no delay.  (Or there shouldn't
> be.)  If, however, I am not online and the message reaches my server, it
> will find I'm not online and see the expires-in as 0 and simply not store
> the message offline.
> That's just my take on it, though.
> --
> Rachel Blackman <rcb at ceruleanstudios.com>
> Trillian Messenger - http://www.trillian.cc/
> _______________________________________________
> Standards-JIG mailing list
> Standards-JIG at jabber.org
> http://mailman.jabber.org/listinfo/standards-jig

Matt "linuxwolf" Miller
JID:	linuxwolf at outer-planes.net
E-MAIL:	linuxwolf at outer-planes.net

- Got "JABBER"? (http://www.jabber.org/)

More information about the Standards mailing list