WCS Docs/Examples

WCS (Web Client Service) is a framework for exposing Jabber functionality to the Web. The modules are categorized into either public (anyone can access it without having a login to the server) or client (requires a login and authentication to the server). There are also modules that convert Jabber information (presence, messages, rosters, and other namespaces) to a more accessible format, often based on the .type of the request.

Public Stuff

• Presence: Dynamic buttons and status indicators
• Message: Public message posting gateway
• Register: Account creation
• IQ: IQ queries to any jid/service
• Chat: Instant two-way chat session
• Conference: Multi-party chat session

Client Stuff

• Session IDs: Authentication and session creation/tracking based on a SID
• Basic Auth: Auth and session tracking using HTTP Basic Auth
• Cache Access: Checking for waiting packets on the server
• Message: Message generation
• Presence: Presence management and access to other's presence info
• Roster: Roster management
• IQ: generic IQ queries
• Raw XML: Uploading XML packets
• Conference: Conferencing access
• XML-RPC: Client XML-RPC access

As a simple test, if you've created the wcstest@snowdeal.org account, you could do a simple basic login and then set your presence available, and send a test message to yourself and check for it. Also, this should be your presence icon if the server is up:

Conversion Formats

• .html: Simple HTML display
• .js: JavaScript array(s) containing the packets
• .xml: Normal Jabber XML
• .htmlx: XML encoded in HTML forms
• .redir: Redirect based on the contents
• XML-RPC: Conversion of Jabber XML to XML-RPC structs
• none: Anything missing an extension type will return an html page with an error message