I've taken a few moments and looked more closely at XEP-0313. A few comments follow, primarily about section "5.1 Simple configuration".
This section can be interpreted as if settings for all jids have to be retransmitted, even if only one change has been made. Doesn't that introduce a possible race condition in case two clients attempt to make an update at the same time? Doesn't that unnecessarily make the transmitted stanza (or a received confirmation of the new preferences) bloated? Is there a reason for the syntax <always><jid>#textnode</jid></always>? Why not, for example, <always jid="#jidhere"/>? Can <always/> and <never/> repeat in the first place? If so, can there be more than one <jid/> in each instance of <always/> and <never/>? A server implementation can get around a lot of issues around configuration by exposing ad-hoc commands. But, that doesn't let a client design a nice UI. And, how does an archive configured using ad-hoc commands map to simple configuration? How does one read the simple preferences without modifying them? With <iq type="get"/>? If so, can that be explicitly stated in the text of the XEP? On Tue, Jun 3, 2014 at 4:42 PM, XMPP Extensions Editor <[email protected]> wrote: > XEP-0313 (Message Archive Management) has been Deferred because of > inactivity. > > Abstract: This document defines a protocol to query and control an archive > of messages stored on a server. > > URL: http://xmpp.org/extensions/xep-0313.html > > If and when a new revision of this XEP is published, its status will be > changed back to Experimental. > -- Ivan Vučica [email protected]
