ejabberd - Comments for "Message delivery status"

XEP-0022

Curufinwe — Wed, 17 Jan 2007 14:52:15 +0000

legoscia wrote:

I found that Kopete returns <delivered/> as well. The list is still not complete, though ☺

I've made some experiments: most of jabber clients (at least exodus, miranda, soapbox) "passively" support it. "passively" means they reply with notification if sender requets it but do not use "delivered" events themself.

legoscia wrote:

The best place for that would probably be in ejabberd_c2s.erl, function handle_info/3, the clause for handling route messages.

Боюсь, что в свете нормальной поддержки расширения клиентами, писать модуль для сервера уже не придётся. А жаль, хотелось поближе познакомиться с эрлангом:(. Большое спасибо за помощь!

In ejabberd_c2s.erl

legoscia — Wed, 17 Jan 2007 12:49:44 +0000

Curufinwe wrote:

Client support for this extention is not an easy information to find, indeed;)

I found that Kopete returns <delivered/> as well. The list is still not complete, though ☺

Quote:

On the other side server-side implementation would give us wider client choice. I've found support for "offline" event notification in mod_offline module. Could you please point for the best place for "delivered" event notification. I know that doing it server-side is not extention complaint, but we don't need that anyway.

The best place for that would probably be in ejabberd_c2s.erl, function handle_info/3, the clause for handling route messages.

XEP-0022

Curufinwe — Wed, 17 Jan 2007 12:42:17 +0000

Thank you! XEP-0022 matches well to our needs.

Client support for this extention is not an easy information to find, indeed;)

XEP-0022

legoscia — Tue, 16 Jan 2007 19:15:59 +0000

I think the easiest way to do that would be to only use clients that implement XEP-0022 fully. This will tell you whenever the recipient's client has received the message. I'm afraid I don't know exactly which clients do this; I only know for sure that jabber.el does and Psi does not.

Or do you mean that this information should be stored on the server? In that case, writing a filter module for ejabberd would probably be the best way, and doable in 20 lines of code. An interface for viewing the information would be more work, though...