Olivier Goffart <[EMAIL PROTECTED]> wrote: > Well, The situation is a bit complex. There is at least 2 XEP involved: > > XEP-0022: Message Events (deprecated) > XEP-0085: Chat state notification > > Thoses are mainly used for the typing notification. Kopete support both > Anyway, only the XEP-0022 include the sending notification, but this > XEP is > deprecated and there is AFAIK no real replacement to this. > > There is no reliable way to know if a client/server support XEP-0022. > (if we > don't receive notification it probably means it doesn't support) > (but on the other hand, if we receive a notification, that means > > There is also the experimental XEP-0198: Stream Management (Kopete > doesn't > support it and I don't know any client which support it) which is > supposed to > be a theorical replacement for the message acknowledgement, but which is > not > really the same thing at all. > > > > Anyway, i don't like the patch either. > The disability should be a property of the ChatSession, not of the > Contact. > > I would say that in the case of jabber, an icon should be set when we > receive > the ack, and the pending notification only if we know the client > support it > (because we already received ack)
I agree with that and will create new patch. For now we don't need the suppress notification patch. > Note that for jabber there are 3 different ack: > - Message has been received > - Message has been displayed > - Message has been stored on the server > (kopete always mark all message as displayed which is a bit wrong) If you are talking about state notification (the new one) this isn't entirely true. We don't do anything if message has been displayed. We could add stored on server state, don't know if displayed state is worth adding (from ICQ/AIM point of view it isn't) Roman _______________________________________________ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
