When an interesting event happens the modules that are subscribed to that event get run. The basic idea behind ejabberd modules is that there are lifecylce events that occur, such as a user coming online, a user going offline, or receiving a message, and a module can subscribe to a particular event. Everything was regularly deployed to a staging environment and compiling ejabberd modules per environment seemed like a maintenance headache.īody with the data needed by the rails app.There were two things I needed it to do a bit differently.Įasily configure the url where the data was being sent. That was originally intended to forward offline messages from ejabberd toĪfter digging into the mod_offline_prowl code, I saw that it could be adapted to do what I needed. In my research, I came across a module for ejabberd called We decided to see if we could get ejabberd to forward the messages for offline users. To handle the communication with Apple's push notification service. Hypothesisīecause we were concurrently developing a rails app to provide theįor the iOS app, we decided the easiest solution would be to forward the offline messages from ejabberd to the rails app and integrate The solution we came up with requires a some integration, but only between 60-70 lines of code. At the time, it didn't seem like there was a great solution to get messages to offline users directly from ejabberd, so we started doing a bit of research. One of the challenges we had to overcome was sending push notifications to offline users when they received an incoming chat message. The decision was made to use ejabberd as the backend for the chat, with a native, I recently had the fortune to work on an iOS application that included a feature to allow users to chat with each other. IOS Push Notifications using Jabber and eJabberd
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |