Provide a seamless and reliable mobile experience

Ejabberd 3.0 provides the ability to connect to mobile applications with a set of reliable mobile features that enables mobile apps to propose a seamless and reliable mobile experience to end users. Ejabberd 3.0 mobile reliability layer helps manage mobile network’s disconnection, message deliveries, consistent conversation on any online device, push notification and mobile interfaces.

• Mobile network’s disconnection managed at server’s level with contacts appearing as being connected to the service within the contact list. With the rebind feature, mobile network’s disconnection is not managed as an end-user service disconnection.
• Push notification capability with alerts sent to end-user’s mobile device via push notification systems like APNS and Google respectively provided by Apple and Google. If end user’s mobile app is not running in the foreground/background, an alert is sent each time a message is received via push feature.
• No message is lost due to a bad network connectivity. Each time a message is sent, the server checks the status of the message delivery with an acknowledgment provided by the mobile app (acknowledgment feature).
• Carbon-copied message allows end user to read all his conversations on each running mobile app (carbon-copy feature).
• Mobile interface libraries for the most used mobile OS, i.e. iOS and Android, to be fully integrated within mobile apps with rebind, push notification for iOS, acknowledgement and carbon-copy.

Improve dramatically performance and scalability

Ejabberd 3.0 provides core optimisations compared to ejabberd open-source 2.1.11 with major rewritings for high availability. All the modules that deal with performance and scalability have been rewritten. This rewriting saves 50% of memory and uses less CPU. In other words, by using the same hardware, ejabberd 3.0 gives you more than 50% of end users!

• Memory improvements: 20% compared to 2.2 release. It is 50% compared to 2.1 open-source release.
• Complete rewriting for the binary support with the handling of internal data by using less memory and avoiding memory replication.
• Cluster is better supported with the use of consistent hashing to get rid of data replication. The result is a more effective approach in internode communications.
• Memory reduction of the data kept in memory for each connected user.
• PubSub broadcast optimisation with reduction of internal data transfer in cluster setup.

Seamlessly connect to the Web

Ejabberd 3.0 supports more interaction with the browser and the web app, facilitating real-time messaging. The use of WebSocket provides the ability to seamlessly send and receive messages while a browser tab is opened. BOSH capability is provided as a fallback for XMPP connection.

• Memory usage has been improved with better buffering
• Faster and lower latency messaging on the web using state of the art protocol (including experimental JSON packets to limit XML costly parsing)

Customise to provide Administration and Statistics

Ejabberd 3.0 simplifies critical administration and key usage statistics through an easy-to-use and customizable management console that enables administrators and product managers to easily access, monitor and render server’s core information or key usages. Ejabberd 3.0 offers these new feature set as part of the TeamLeader application console.

• Default dashboard improved
• Default interface replaced by monitoring tool

Integrate easily with your applications

Now all ejabberd main features like mobile reliability features for instance are accessible from any mobile app or webpage thanks to API interfaces. Ejabberd 3.0 provides libraries, for web pages and mobile apps, to be easily integrated within your own source code. Ejabberd 3.0 simplifies the mean to integrate with any back-end system via a new simple data-structured interface.

• Mobile libraries for iOS and Android
• Web library with WebSocket support and fallback to BOSH support
• XML-RPC and ejabberdctl front-end commands
• Ease of development: Build an app in weeks instead of months.

Want to know more?

Contact us