[JDEV] delayed messages

[Keith Minkler]

I've had a similar discussion with jer about routing messages to a user, back when "offline presence" used to exist.. and I wanted my client to discern between a user going offline, and a user sending their offline presnece..

what it boiled down to, was i wanted the *sender* to be able to decide where the message ultimatly ended up.. however.. thanks to jer (and his brainwashing? =]) I came to realilze that it's not up to the sender where *they* want the message to go, it's up to the *receiver* to choose where *the reciever* wants the messages to show up..  

this is why mod_filter came into existance, out of the primitive "offline presence" model... so that a user has ultimate control over where his messages are being sent.

if you don't want messages to be stored offline, or to alert the sender, you can add a filter rule, such as <rule name="warn about offline storage"><unavailable/><offline/><reply>The Message you just sent is being stored offline until the user is available to fetch it</reply></rule>  this will still store the messages offline when you are unavailable, but it will also send back a message to the sender, indicating the "delivery problem".


> With a store-and-forward architecture, there has got to be some way to
> expire messages.  What happens to messages if they can't be delivered?

if messages *cannot* be delivered, for any reason, (offline storage *is* delivery) the message gets bounced back to the sender 

there is no way in the server to 'expire' messages... nor is there any need that I see.. I suppose in the future, I can implement a timeout on offline messages, such as <offline timeout="60"/> in your filter rules..

Keith Minkler

On Sat, Sep 09, 2000 at 11:35:29AM -0700, Bill Abbas wrote:
> 
> This isn't something I want to go in and hack, either now or later :-)
> 
> With a store-and-forward architecture, there has got to be some way to
> expire messages.  What happens to messages if they can't be delivered?
> 
> Bill
> 
> 
> mark at mjwilcox.com wrote:
> > 
> > Haven't looked exactly at the code to do this, but you'd probably
> > have to hack something into the Jabber server.
> > 
> > Basically you could customize the server not to send anything to
> > anyone who's not online.
> > 
> > Or better, add a tag to your message that says:
> > <time-critical/>
> > 
> > if that tag is visible and the person isn't online, then they don't get
> > it. Otherwise they do (get the message if they aren't currently
> > online).
> > 
> > I'd wait until 1.2 comes out to really do anything like this on the
> > server. Trust me, you don't want to hack anything into the 1.0
> > server. I've spent the last 6 weeks doing that... ;)
> > 
> > Mark
> > 
> > On 8 Sep 00, at 18:11, Bill Abbas wrote:
> > 
> > >
> > > >From the JPG:
> > >
> > > "If a message or presence is sent to an offline Jabber entity, the
> > > server stores it. When the entity comes online, the data is deliverd."
> > >
> > > Couple of questions:
> > >
> > > I've seen this happen in Gabber, but not in my ICQ client.  Does this
> > > deferred delivery apply to packets being routed through transports, as
> > > well?
> > >
> > > How does one control this feature?  I want to programmatically disable
> > > it from the sending side, so that the only people who get certain
> > > time-sensitive messages are ones who are currently online.
> > >
> > > Thanks.
> > >
> > > Bill
> > >
> > > _______________________________________________
> > > jdev mailing list
> > > jdev at jabber.org
> > > http://mailman.jabber.org/listinfo/jdev
> > >
> > >
> > 
> > Mark Wilcox
> > mark at mjwilcox.com
> > Got LDAP?
> > 
> > _______________________________________________
> > jdev mailing list
> > jdev at jabber.org
> > http://mailman.jabber.org/listinfo/jdev
> 
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev