[jdev] message events + chat state notifications
stpeter at jabber.org
Fri Nov 3 14:40:07 CST 2006
Olivier Goffart wrote:
> Le vendredi 3 novembre 2006 18:36, Peter Saint-Andre a écrit :
>> IMHO it's about time to actively deprecate the old message events
>> protocol (XEP-0022) in favor of chat state notifications (XEP-0085).
> But 85 and 22 are IMO two completely different things.
> Appart the composing notification, they covers different layer.
> XEP-0022 is usefull to let know that the user has actually read the message,
> or if the message is stored offline. XEP-0085 doesn't let you do that.
> Maybe the composing event should be marked as deprecated in xep-0022 , but i
> don't think the whole xep-0022 should be deprecated.
The methods in XEP-0022 are fully obsoleted by the combination of the
1. <composing/> -- XEP-0085
2. <offline/> -- XEP-0079
3. <delivered/> -- XEP-0184
4. <displayed/> -- I don't think this was ever used (and I don't think
there's a valuable difference between <delivered/> and <displayed/>)
You might ask: why do we need three specs to obsolete XEP-0022?
The answer is: because XEP-0022 was a hodgepodge of functionality and
wasn't well designed in the first place.
> Personally, in Kopete, I do support both 22 and 85, and i use both of them all
> the time.
All the time? Even if the other party doesn't support them? IMHO that's
not very network-friendly...
Jabber Software Foundation
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 7358 bytes
Desc: S/MIME Cryptographic Signature
More information about the JDev