Difference between revisions of "Platform Team/Prosody"
| Line 34: | Line 34: | ||
See sugar-server-base [http://git.sugarlabs.org/server/base/blobs/master/etc/020.jabber/prosody.d/ sources] for configuration example. | See sugar-server-base [http://git.sugarlabs.org/server/base/blobs/master/etc/020.jabber/prosody.d/ sources] for configuration example. | ||
| + | |||
| + | == TODO == | ||
| + | |||
| + | * Dynamically remove users from sugar roster if they are offline for some reasonable time. | ||
| + | * Compare Prosody resources consumption with existed ejabberd. | ||
== Resources == | == Resources == | ||
Revision as of 06:36, 21 July 2011
Purpose
The reasons to use Prosody Jabber/XMPP server:
- be humble for consuming memory and CPU resources, especially for Sugar Server usecase (up to 1K users),
- jabber server should be simply initially configured and work in unmaintained mode as long as possible.
Plugins
These plugins are tested against Prosody 0.8.2 version.
mod_sugar_roster
Provides global roster when every user sees all registered accounts.
mod_sugar_muc
The only difference in comparing with original mod_muc plugin is a workaround for
telepathy-gabble/Prosody issue.
This plugin should be used instead of mod_muc until issue will be fixed in telepathy-gabble or in Prosody.
mod_sugar_saslauth
Original mod_saslauth plugin with preventing multiple auth from the same jid. See sm_make_authenticated() function in its sources.
This plugin should be used instead of mod_saslauth until more lightweight implementation is found.
Installation
To reuse sugar plugins, copy them to the directory with Prosody plugins. Or, install prosody-sugar package from Sugar Server repository.
Configuration
See sugar-server-base sources for configuration example.
TODO
- Dynamically remove users from sugar roster if they are offline for some reasonable time.
- Compare Prosody resources consumption with existed ejabberd.