| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
| Name | Name | Last commit date | ||
|---|---|---|---|---|
The messaging framework is introduced as a component that follows a client/server architecture, which can easily be integrated with any application server for sending JSON-based notifications to any mobile platform that implements a XMPP mobile client. Unlike GCM, APNS or MPNS, XMPP-based notification server is not constrained by number of messages that can be pushed to a mobile or a specific mobile platform.
Openfire or ejabber (Gateway broker) - Here you can find a guide to configure Openfire 3.7.1
Maven2
Web server (e.g. GlassFish, Tomcat, JBoss, etc.)
$ git clone https://github.com/huberflores/XMPPNotificationServer.git$ cd ~/XMPPNotificationServer/$ mvn install$ cd ~/xmpp-notification/target/xmpp-notification/WEB-INF/$ nano web.xml<web-app>
<servlet>
<servlet-name>xmppnotification</servlet-name>
<servlet-class>ee.ut.notification.xmpp.server.RESTNotification</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>xmppnotification</servlet-name>
<url-pattern>/xmppnotification</url-pattern>
</servlet-mapping>
</web-app>Configure Openfire/XMPP server
$ ~/xmpp-notification/target/xmpp-notification$ nano server.propertiesserver=your-xmpp-server
domain=your-xmpp-domainBuild war file
Locate war file within your Web server
In order to try the messaging framework, install the XMPP mobile client in a device and execute the xmppload.sh script.
$ ./xmppload.shThe complete framework (Client/Server) was built for comparison purposes with other notification mechanisms. If you are using the tool for your research, please do not forget to cite. Thanks!
| Back | FazBrowse Home | New Git URL |