I tried to debug but hardly have any knowledge of erlang.
i have generated mod_archive.beam file by compiling mod_archive.erl and put this file in Applications/ejabberd-13.12/lib/ejabberd-13.12/ebin (mac os).īut when start module i got following crash report.Įxception exit: , i have downloaded ejabberd modules and follow the step in.
EJABBERD SAVE PENDING MESSAGES ON SERVER INSTALL
Tutorial to install Datasink, a Perl based alternative for mod_archive.Old document advocating for server-side history storage: Jabber Client Design: Message History.Support for JEP-0136: Message Archiving.Web reader Php web interface Related Links
EJABBERD SAVE PENDING MESSAGES ON SERVER UPDATE
An update on JWChat is expected in the mid-term. Support of XEP-136 on Jabber clients JWChat Implemented, but does not work, since it implements an old version. Options save_default true or false: whether or not messages should be saved by default session_duration The time in seconds before a session timeout (for a collection). User may enable/disable automatic archiving for one contact or globally.Olivier Goffart, Alexey Shchepin and Alexander Tsvyashchenko You can find thoses modules in ejabberd-modules There is also the module mod_archive_webview which is a web interface to mod_archive_odbc (for vieweing the logs) Now I've deleted onedrive and the folder containing the file, because I've left that job. Deleting the file or replacing it with a dummy file doesn't work. mod_archive_odbc uses MySQL or SQLite3, and includes other improvements One of the files from there is stuck on 'upload pending' and I tried every option to get rid of it with no joy.The main difference between them is the storage method: There are three different versions of this module. As a summary, mod_archive allows a Jabber client to request the server to store his own conversations, and later request them. Later, the client can request to the server the messages. XEP-0136 proposes that the Jabber server archives the messages as they pass through the server, if the Jabber client requested it. But sometimes this isn't possible or affordable, for example when using a mobile phone, or in a public access machine. Usually Jabber clients can store the conversations in the user hard drive. In return, no server support for this feature is required-it's implemented solely in the clients.Mod_archive implements XEP-0136 version 0.6 except otr (off-the-record). The latter one is bullet-proof as the clients rely on explicit notifications about message reception. Note that this is not bullet-proof anyway as there is a window between the moment the target client losts its connectivity with the server and the moment the TCP stack on the server's machine detects this and tells the server about it: during this window, everything sent to the client is considered by the server to be sent okay because there's no concept of message boundaries in the TCP layer and hence if the server process managed to stuff a message stanza's XML into the system buffers of its TCP connection, it considers that stanza to be sent-there's no way for it to know which bits of its stream did not get to the receiver once the TCP stack says the connection is lost.
The former one requires an AMP-enabled server implementation and the initiating client has to be able to tell the server what kind of delivery status reports it wants (it wants an error to be returned if the delivery is not possible). One way is to employ the Advanced Message Processing (AMP) on your server another one is to employ the Message Delivery Receipts on your clients.