http://prosody.im/ 2010-03-10T17:01:14+00:00 http://prosody.im/ http://prosody.im/lib/images/favicon.ico text/html 2010-03-08T15:42:36+00:00 Matthew Wild http://prosody.im/testimonials?rev=1268062956&do=diff People are talking about Prosody, we love it! Here are some of the nice words they have to say... ---------- “Tried Prosody earlier today. Colour me impressed.” @kev ---------- “Prosody is seriously cool. You just dont get used to not having to compile the server for changes” @jcdickinson text/html 2010-03-05T12:25:43+00:00 Matthew Wild http://prosody.im/doc/cyrus_sasl?rev=1267791943&do=diff Introduction XMPP uses a standard authentication protocol called 'SASL' to validate client credentials. Prosody has a built-in SASL library, and uses this by default to validate credentials against Prosody's internal account store. Alternatively since 0.7 Prosody supports using Cyrus SASL, an external SASL provider which can validate user-supplied credentials against other sources, such as PAM, LDAP, SQL and more. It also allows the use of GSSAPI for single-sign-on services. text/html 2010-03-01T00:44:34+00:00 Matthew Wild http://prosody.im/doc/configure?rev=1267404274&do=diff Prosody's configuration is held in a single file, prosody.cfg.lua. If you install Prosody under GNU/Linux then you should find it in /etc/prosody/prosody.cfg.lua. On other systems, or when not installed, it will be under the same directory as the prosody main executable. text/html 2010-02-27T19:22:23+00:00 Matthew Wild http://prosody.im/doc/packagers?rev=1267298543&do=diff Prosody's main goal is to be user-friendly and easy to use. One of the hardest parts of this task is getting the server installed and running in the first place. By providing reliable high quality packages then on most systems installing Prosody should take no more than a minute of the user's time. text/html 2010-02-27T16:34:14+00:00 Waqas Hussain http://prosody.im/doc/port_multiplexing?rev=1267288454&do=diff Prosody can handle multiple protocols on a single port. This allows you to offer both XMPP and HTTP on port 80 for example. Usage To use multiplexed ports, use the 'ports' and 'ssl_ports' option in the configuration file: The following makes Prosody accept HTTP, XMPP client, XMPP server and XMPP component connections on each of these three ports: text/html 2010-02-27T15:35:21+00:00 Matthew Wild http://prosody.im/doc/depends?rev=1267284921&do=diff Prosody depends on other applications or libraries to allow certain functionality. This page describes the different runtime dependencies we have, what they are for, and how to get hold of them if you don't have them. Note: If you are trying to build Prosody from source then you will need additional dependencies, please see Installing from source for a short how-to. text/html 2010-02-27T15:31:49+00:00 Matthew Wild http://prosody.im/doc/libevent?rev=1267284709&do=diff Introduction Prosody's core task is to handle multiple client or server connections, and handle incoming data from those connections. Monitoring lots of connections for incoming data efficiently isn't a trivial task, and although the standard POSIX API provides select() and poll() for this task, neither scale well for increasing connection counts.