[jdev] deferred delivery

Tijl Houtbeckers thoutbeckers at splendo.com
Mon Mar 7 10:55:56 CST 2005

On Mon, 07 Mar 2005 03:28:33 -0700, Jeremy Nickurak  
<atrus at jabber.spam.rifetech.com> wrote:

> On lun, 2005-02-28 at 21:04 +0100, Tijl Houtbeckers wrote:
>> Jabber is instant, near real time. So this means you're get a near real
>> time "instant failure", if your message can not be delivered. This  
>> opposed
>> to email where failure isn't "instant" at all, if you send a message it
>> can stay in the queue for up to 2 weeks and there is nothing you can do
>> about it. This is why SMTP uses a store-and-forward architecture.
> jabberd has offline storage for when a user is offline. The message gets
> silently stored, and delivered once the user logs in. This does not
> happen when the server is offline. To me, this seems a fairly
> straightforward double-standard.

This is true for messages, and servers that have this feature enabled.  
It's not true for Jabber's general processing (stanzas). Currently you can  
get a notification from some servers if your message is stored offline  
(JEP-22). The future protocol for this will be AMP (Advanced Message  
Processing, JEP-79). With this you can also prevent your message from  
being stored.

SO I agree with you, that in practise, jabberd does have a "double  
standard" when it comes to this. It's exactly why protocols such as IBB  
are unusable. Hopefully AMP will fix that in the future. I still can't  
read that JEP without getting a headache though.

Question for the list: Are there any opensource servers out there that  
support AMP?

More information about the JDev mailing list