Am 28.05.2013 22:44, schrieb XMPP Extensions Editor:
The XMPP Extensions Editor has received a proposal for a new XEP.
Title: Chat Markers
Abstract: This specification describes a solution of marking the last received,
read and acknowledged message in a chat.
URL: http://xmpp.org/extensions/inbox/chat-markers.html
quick glance:
section 2:
The term "active chat" refers to a chat that a user is currently active in.
-- doesn't 0085 have a definition of that?
section 4:
read -- the message the user has viewed it in a active chat.
s/the message//
displayed -- the message has been displayed to the user in an
active chat
would be easier to define than "the user has viewed it"
section 6.1:
can this be more aligned with what we have in carbons? E.g.
<iq xmlns='jabber:client'
type='set'
id='enable1'>
<enable xmlns='urn:xmpp:chat-markers:tmp'/>
</iq>
Design-wise I'd prefer <message/> to <iq/>. But I think the rule not to
store bodyless messages is wrong and therefore ignore that. The offline
use-case is important however.
<message/> in combination with carbons might fulfill the multi-client
usecase better.
