[Standards] LAST CALL: XEP-0136 (Message Archiving)

Peter Saint-Andre stpeter at stpeter.im
Mon Apr 14 23:22:37 UTC 2008

Alexander Tsvyashchenko wrote:
> Hello All,
> Quoting Alexey Melnikov <alexey.melnikov at isode.com>:
>>>> In section 4.2:
>>>>> Note: The content of <message/> elements that have different thread
>>>>> IDs SHOULD be archived in separate collections.
>>>> Is this a requirement on the client or on the server?
>>> I think it is a client requirement.
>> Then don't use passive voice, e.g.
>> Note: The client SHOULD archive the content of <message/> elements that
>> have different thread
>> IDs in separate collections.
> As 4.2 is "general description" of collections requirements and behavior
> I would say this requirement is both for client and server depending on
> archiving scenario, no?
> If the auto-archiving is activated - this is certainly server-side
> behavior, it is covered by the previous discussion we had on this list
> related to <thread> treatment.
> If manual archiving is used - then it's indeed client's task to handle
> that correctly.

That seems sensible to me.


Peter Saint-Andre

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7338 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20080414/364a8150/attachment.bin>

More information about the Standards mailing list