Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

poe::component::jabber::xmpp(3pm) [debian man page]

POE::Component::Jabber::XMPP(3pm)			User Contributed Perl Documentation			 POE::Component::Jabber::XMPP(3pm)

NAME
POE::Component::Jabber::XMPP - connect using the XMPP Jabber protocol SYNOPSIS
This is a Protocol implementation for the specifics in the XMPP protocol during connection initialization. DESCRIPTION
PCJ::XMPP provides all the mechanisms to negotiate TLS, SASL, resource binding, and session negotiation that PCJ needs to successfully establish an XMPP connection. In essence, it implements XMPP Core and a smidgeon of XMPP IM. METHODS
Please see PCJ::Protocol for what methods this class supports. EVENTS
Listed are the exported events that make their way into the PCJ session: set_auth This handles the initial SASL authentication portion of the XMPP connection. init_input_handler This is our entry point. This is what PCJ uses to deliver events to us. build_tls_wheel If TLS is required by the server, this is where that negotiation process happens. challenge_response This handles the subsequent SASL authentication steps. binding This handles the resource binding session_establish This handles session binding. NOTES AND BUGS
Currently, only DIGEST-MD5 and PLAIN SASL mechanisms are supported. Server implementations are free to include more strigent mechanisms, but these are the bare minimum required. (And PLAIN isn't /really/ allowed by the spec, but it is included because it was a requested feature) The underlying backend has changed this release to now use a new Node implementation based on XML::LibXML::Element. Please see POE::Filter::XML::Node documentation for the relevant API changes. AUTHOR
Copyright (c) 2003-2009 Nicholas Perez. Distributed under the GPL. perl v5.12.4 2011-08-09 POE::Component::Jabber::XMPP(3pm)

Check Out this Related Man Page

POE::Component::Jabber::ProtocolFactory(3pm)		User Contributed Perl Documentation	      POE::Component::Jabber::ProtocolFactory(3pm)

NAME
POE::Component::Jabber::ProtocolFactory - protected helper class to handle different protocols SYNOPSIS
PCJ::ProtocolFactory is a protected helper class used to instantiate specific Protocols based on exported constants DESCRIPTION
PCJ internally uses PCJ::ProtocolFactory to turn the ConnectionType argument into a Protocol object used to implement the various supported dialects. This is why the accepted arguments are exported as constants upon use. FUNCTIONS
By default no functions are exported beyond the accepted arguments. Only a package function is available: get_guts [Protected] get_guts takes a single argument and that is a defined constant exported by this module. It returns a PCJ::Protocol object. See PCJ::Protocol for details on its methods and implementing different Protocols. CONSTANTS
Below are the constants that are exported. Their names are rather self-explanatory: XMPP LEGACY JABBERD14_COMPONENT JABBERD20_COMPONENT NOTES
All supported Protocol types are implemented herein. get_guts will confess if it receives an invalid argument. AUTHOR
(c) Copyright 2007-2009 Nicholas Perez. Released under the GPL. perl v5.12.4 2011-08-09 POE::Component::Jabber::ProtocolFactory(3pm)
Man Page