![]() Note: while a service might have many "archives" as defined here (one per JIDĬapable of being queried) this is a conceptual distinction, and a server is not bound to any particular Through ad-hoc commands depending on the server implementation.Īn archive contains a collection of messages relevant to a particular XMPP address, e.g. ![]() Advanced configuration however may be performed Which allows for a simple user interface in clients. Implementations, and hence the configuration protocol in this specification is much simplified, This feature was deemed unnecessary for the majority of Server logic for not including encrypted or specially-tagged messages in the archive (out of scope for Equivalent functionality can be implemented with So this specification does not try and regulate that. In reality the archiving behaviour of a contact's server cannotīe enforced (they could ignore the OTR request and archive the messages anyway without your consent) This allowed complex negotiation for either the user or contact to command specificĬonversations to bypass the archive. Support for 'off the record' chats (OTR not to be confused with the encryption algorithm of.May be defined in a future specification if there is demand for such functionality. Uploading could be useful for bootstrapping an empty archive however, and Messages to and from the client, it is typically rare for a client to end up with messages that are On the assumption that a server automatically archives It is possible to apply the logic for splitting a stream of messages into conversations on theĬlient-side, thus greatly simplifying the protocol. Few clients even support this concept for local history storage, and Notable functionality in XEP-0136 that is intentionally not defined by this specification for simplicity: Protocol if it so chooses, though a mapping between both protocols is beyond the scope of this specification. ![]() ![]() Should be noted that (although not required) a server is free to implement XEP-0136 alongside this Through this it is hoped to boost implementation and deployment of archiving in XMPP. This specification aims to define a much simpler and modular protocol for working with a server-side Shown that the protocol defined therein supports rather more functionality than is typically needed for theĪbove uses, and is significantly more effort to implement. Naturally in the message log as the user scrolls back in time.Īnother extension for archiving already exists in XMPP, Message Archiving (XEP-0136) ). So-called 'infinite' scrollback, whereby a client automatically fetches and displays historical messages.Calendar-based on-demand display of historic messages in a client that doesn't keep local history.Automatic history synchronization between multiple clients.The resulting protocol was designed to allow for the following primary 2.Īs this extension aims to make things easy for client developers, some research was made into the Multiple clients, to read the history of a MUC room, or to view old items in a pubsub node. Support local history storage, to synchronise conversation history seamlessly between This feature allows them to record conversations that take place on clients that do not It is a common desire for users of XMPP to want to store their messages in a central archive Including groupchat results in a user archive.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |