External server-side components.
Most Jabber server implementations allow for add-on components that act as a separate entity on the Jabber network, but use the server-to-server functionality of a regular Jabber IM server. These so-called 'external components' are connected to the Jabber server using the Jabber Component Protocol as defined in JEP-0114.
This module allows for writing external server-side component by assigning one or more services implementing ijabber.IService up to ServiceManager. The ServiceManager connects to the Jabber server and is responsible for the corresponding XML stream.
| Class | ComponentInitiatingInitializer |
External server-side component authentication initializer for the initiating entity. |
| Class | ConnectComponentAuthenticator |
Authenticator to permit an XmlStream to authenticate against a Jabber server as an external component (where the Authenticator is initiating the stream). |
| Class | ListenComponentAuthenticator |
Authenticator for accepting components. |
| Class | Router |
XMPP Server's Router. |
| Class | Service |
External server-side component service. |
| Class | ServiceManager |
Business logic for a managed component connection to a Jabber router. |
| Class | XMPPComponentServerFactory |
XMPP Component Server factory. |
| Function | buildServiceManager |
Constructs a pre-built ServiceManager, using the specified strport string. |
| Function | componentFactory |
XML stream factory for external server-side components. |
| Constant | NS_COMPONENT_ACCEPT |
Undocumented |
| Parameters | |
componentid:unicode | JID of the component. |
| password:str | password used to authenticate to the server. |