Programming Jabber

Component Instance: sessions

The sessions component, described by the configuration XML shown in Example 4-8 and shown in diagram form in Figure 4-5, provides Session Management features for users (the word “users” is employed in the widest possible sense—a user could be a person or a script) connecting with Jabber clients, through XML streams identified with the jabber:client stream namespace.

Figure 4-5. Diagram view of sessions component instance

The component also provides the services that give Jabber its IM capabilities— services such as roster management, message filtering, store-and-forward (“offline”) message handling, and so on. These IM services are loaded individually as part of the component connection phase.

Example 4-8. jabber.xml configuration for the sessions component instance

<service id="sessions"> <host><jabberd:cmdline flag="h">yak</jabberd:cmdline></host> <jsm xmlns="jabber:config:jsm"> <filter> <default/> <max_size>100</max_size> <allow> <conditions> <ns/> <unavailable/> <from/> <resource/> <subject/> <body/> <show/> <type/> <roster/> <group/> </conditions> <actions> <error/> <offline/> <forward/> <reply/> <continue/> <settype/> </actions> </allow> </filter> <vCard> <FN>Jabber Server on yak</FN> <DESC>A Jabber Server!</DESC> <URL>http://yak/</URL> </vCard> <register notify="yes"> <instructions>Choose a userid and password to register.</instructions> <name/> ...