messaging application, which makes use of Ejabberd (XMPP) server. Not sure which one was responsible for logging, but I believe to upgrade them all is essentially a good idea. Ive upgraded all my installed erlang- packages and logging started to work. Now user 1 texting user 2 when user 2 is in Offline : So these message are saved in database along with composing message. Well, my suspicions were right, some erlang package should be upgraded to the version from the Testing repository. User 1 texting User 2 when User 2 is in Online : user 2 receives typing status and message asap. Since ejabberd 20.12, this command is asynchronous: the API call may return before the server has send all the invitations. This use of the archive table is cleaner and it makes it possible for clients to slowly drop the former offline use case and rely on message archive instead. Arguments: host:: string : Name of host where operation should be aborted Result: status:: string : Status text Tags: purge. Enabling this option will make modoffline not use the former spool table for storing MucSub offline messages, but will use the archive table instead. After updating from image 20.04 to 21.04 I wasnt able to start a bosh sessions anymore, after that i rolled the image back to 20.04 and I still unable to start the session. A new ejabberd release is finally here ejabberd 22.05 includes five months of work, 200 commits, including many improvements (MQTT, MUC, PubSub. If a message cannot be delivered immediately (for example, if you are offline). And i got an requirement now where i should not store offline composing message in database can you help me out please. Abort currently running delete old offline messages operation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |