Ejabberd vs openfire performance install#

The leaders of both projects (Fred Dixon and Marc Laporte) met 2 or 3 times over a few years to try to find a way to make it work. Still in 2017, the Flash version is the main one, and the HTML5 version is not ready for prime time Now OK, and developedДЇor WikiSuite, it's critical to also cover all the other use cases above.No presence feature (it's for a scheduled class, and not ad hoc collaboration).BigBlueButton is a distance education tool. While Openfire Meetings and BigBlueButton broadly share the same feature set (videoconferencing, screensharing, etc), there are fundamental difference. Tiki Wiki CMS Groupware has built-in (but optional) integration with BigBlueButton since Tiki 5 (2010), and the two communities worked closely together for a tight integration and thus, for WikiSuite, this would have been the simple option. Desktop client: PГ dГ©, a Chrome extension with tons of features.Server-side: Openfire + Converse (XMPP) with Jitsi Meet (WebRTC).We ultimately want WikiSuite to be awesome at covering all the use cases above, and we do so by mostly combining: Generally satisfies the usual component criteria.

Ejabberd vs openfire performance install#

Over 1 million install (just via Docker pull!).

WebRTC support (via inclusion of Jitsi Meet).

XMPP support, and thus presence (using standards).

We picked Openfire for the following reasons: Remote login and management, even unattended

Difficult to install software on their computer. To route request to someone who is available. Team member must give permission to take control of computer (ex: for 30 minutes) Easier to install software on their computer. Help desk for team members (Remote Assist) Meeting notes (meeting agenda, and live collaborative note taking for decisions) Presence, and can escalate to audio / video / screensharing as needed