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::J14(3pm) User Contributed Perl Documentation POE::Component::Jabber::J14(3pm)NAME
POE::Component::Jabber::J14 - connect to the jabberd14 router as a service
SYNOPSIS
PCJ::J14 is a Protocol implementation that connects as a service to a jabberd14 server.
DESCRIPTION
PCJ::J14 authenticates with the server backend using the method outlined in XEP-114 (Jabber Component Protocol)
[http://www.xmpp.org/extensions/xep-0114.html]
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 event constructs and sends the <handshake/> element for authentication.
init_input_handler
This is out main entry point that PCJ uses to send us all of the input. It handles the authentication response.
NOTES AND BUGS
This only implements the jabber:component:accept namespace (ie. the component initiates the connection to the server).
Also be aware that before this protocol was documented as an XEP, it was widely implemented with loose rules. I conform to this document.
If there is a problem with the implementation against older server implementations, let me know.
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::J14(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)