On this page you'll find information on the three Web Applications used to access an M-Link server from any modern web browser. These applications are designed to support both desktop and mobile devices.

The M-Link application suite includes three JavaScript web applications. These applications connect to M-Link using XMPP running over BOSH [Bidirectional streams Over Synchronous HTTP] . M-Link can support BOSH with or without TLS as described on the M-Link server page.

The M-Link Web Applications can be hosted on a suitable Web Server to allow easy distribution, the browser will download the application from the Web Server. Then the Web Browser will run the M-Link Web Application which will connect to an M-Link server.


The web interface to M-Link statistics allows for lightweight monitoring of M-Link without the need to install any software, to complement the general purpose management and monitoring capability provided by M-Link's Management GUI, M-Link Console. It provides live data to give a concise summary of the operational state of a single M-Link service.

M-Link PubSub Access Control can be used to control which users can access this service.

Message Archive Browser

The Message Archive Browser allows end-users access tohistorical messages in the M-Link archives. This Web Application accesses message history using MAM (Message Archive Management) specified in XEP-0313. Access to a web interface is particularly helpful in environments where some or all deployed XMPP end user clients do not support MAM. More information can be found in the whitepaper [XMPP Archive and Search].

Form Discovery and Publishing

M-Link supports flexible forms publishing and distribution using the protocol defined in XEP-0346: Forms Discovery and Publishing (FDP). FDP templates are managed within M-Link Console and both GUI and browser tools are available that allow users to discover FDP form templates, publish forms, and show published forms.


A Form Discovery and Publishing evaluation guide is available, in PDF format, from the Documentation page of this website.