The O'Reilly Programming Jabber book by DJ Adams is a good read, but woefully out of date. Parts of PCJ (and POE::Filter::XML especially PFX::Node) draw heavily in inspiration from Jabber::Connection (DJ Adams' code he uses as an example).
I haven't read any of the more contemporary Jabber books, but there really is no better source than the RFCs for XMPP. They are quite easy to read and provide example narratives for all the various little steps along the way. And the reason it is under Client is because it makes an outbound connection to a server and not actively listening for connections (jabber:component:connect /is/ another namespace but rarely, if ever, used. In that namespace, the server actually connects to the service that is listening for it). At the end of the day, Client::Component and Client::J2 are just clients only without session management since the server does all of the heavy lifting when it comes to account management, packet routing, etc (the exception is of course when it comes to 'transports' or gateways to other proprietary networks, where the component maps and manages jabber-to-[insert other network] sessions) If what you want is to code up some simple jabber scripts, it might behoove you to take a look at Net::Jabber (shudder) or even some of the command line jabber message senders. While PCJ can be and has been used for such things, its scope is typically the foundation for more complex tasks. See http://punjab.sourceforge.net/ for a good example of someone using PCJ as the foundation to build a more robust client. On 1/17/07, Matt Hicks <[EMAIL PROTECTED]> wrote:
On 1/17/07, Nicholas Perez <[EMAIL PROTECTED]> wrote: > > You have to understand a little bit about how the various Client > classes work and also a bit how the various 'dialects' of the protocol > work. Agreed, I don't understand jabber well enough. > Also with the Component class, it speaks a much simpler dialect > than the others when it comes to authenticating. See > http://www.xmpp.org/extensions/xep-0114.html for more information. If I understand correctly, could I suggest PoCo::Jabber::Server::Component instead of PoCo::Jabber::Client::Component? > ...isn't as good as it could be, but I never expected to be giving Jabber > 101 lessons in the POD. I think Jabber 101 lessons are rightfully "beyond the scope of this POD." I have a copy of the O'Reilly Jabber book *somewhere*... --Matt
