poe::component::jabber::legacy(3pm) [debian man page]
POE::Component::Jabber::Legacy(3pm) User Contributed Perl Documentation POE::Component::Jabber::Legacy(3pm)NAME
POE::Component::Jabber::Legacy - connect using the pre-XMPP Jabber protocol
SYNOPSIS
PCJ::Legacy is a Protocol implementation for the legacy (ie. Pre-XMPP) Jabber protocol.
DESCRIPTION
PCJ::Legacy implements the simple iq:auth authentication mechanism defined in the deprecated XEP at
http://www.xmpp.org/extensions/xep-0078.html. This Protocol class is mainly used for connecting to legacy jabber servers that do not
conform the to XMPP1.0 RFC.
METHODS
Please see PCJ::Protocol for what methods this class supports.
EVENTS
Listed below are the exported events that end up in PCJ's main session:
set_auth
This handles construction and sending of the iq:auth query.
init_input_handler
This is our main entry point. This is used by PCJ to deliver all input events until we are finished. Also handles responses to
authentication.
NOTES AND BUGS
Ideally, this class wouldn't be necessary, but there is a large unmoving mass of entrenched users and administrators that refuse to migrate
to XMPP. It largely doesn't help that debian still ships jabberd 1.4.3 which does NOT support XMPP.
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::Legacy(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)
Is there anyone who still uses CMI to connect to the legacy system , my c applications do uses the binaries and libraries for using the CMI functionality but i do not have access to the original source code , and since this is a very old stuff , i just could not get any source to get to knwo the... (0 Replies)
We have a legacy software application that runs on SCO OpenServer 5.0.6, and the current server (built around 2003-04) is still running. I have been attempting to upgrade the hardware, to hopefully increase the time that we will have access to the data in this system, but am running into an... (13 Replies)
Hi Folks,
Just a quick question here, about Legacy Zones. Well more about how to determine if you are actually in one, on logging into a legacy zone - is there a quick way of checking that?
Regards
Gull04 (7 Replies)