AnyEvent::XMPP::Ext - Extension baseclass and documentation
This module also has documentation about the supported extensions and also is a base class for all extensions that can be added via the
add_extension method of the classes that derive from AnyEvent::XMPP::Extendable.
(That are: AnyEvent::XMPP::Client,
AnyEvent::XMPP::Connection and AnyEvent::XMPP::IM::Connection)
This method can be overwritten by the extension and should return a list of namespace URIs of the features that the extension enables.
This is the list of supported XMPP extensions:
This extension handles data forms as described in XEP-0004. AnyEvent::XMPP::Ext::DataForm allows you to construct, receive and answer data forms. This is neccessary for all sorts of things in XMPP. For example XEP-0055 (Jabber Search) or also In-band registration.
This extension allows you to send service discovery requests and define a set of discoverable information. See also AnyEvent::XMPP::Ext::Disco.
This extension allows the retrieval and storage of XMPP vcards as defined in XEP-0054. It is implemented by AnyEvent::XMPP::Ext::VCard.
This extension allows to receive and send out of band data URLs and provides helper functions to handle jabber:x:oob data. See also AnyEvent::XMPP::Ext::OOB.
This extension lets you register new accounts "in-band". For details please take a look at AnyEvent::XMPP::Ext::Registration.
After lots of sweat and curses I implemented finally iq auth. Unfortunately the XEP-0078 specifies things that are not implemented, in fact the only server that worked was openfire and psyced.org.
So I de-analyzed the iq auth and now it just barfs the IQ set out on the stream with the username and the password.
If you insist on XEP-0078 behaviour enable the
anal_iq_auth option when creating the stream.
You can also completely disable iq auth, well, just see the documentation of AnyEvent::XMPP::Connection
Implemented some functions to deal with XMPP timestamps,
They are meant as simple formatters for you, you will still need to handle timezone stuff and such yourself.
"A mapping to enable legacy entities to correctly handle errors from XMPP-aware entities."
This extension will enable sending of the old error codes when generating a stanza error with for example the
write_error_tag method of AnyEvent::XMPP::Writer.
Also if only the old numeric codes are supplied the AnyEvent::XMPP::Error::Stanza class tries to map the numeric codes to the new error conditions if possible.
See also XEP-0203 below.
The ability to answer to software version, name and operating system requests and being able to send such requests is implemented in AnyEvent::XMPP::Ext::Version.
This extension allows you to connect to a server as a component and makes it possible to implement services like pubsub, muc, or whatever you can imagine (even gateways). See documentation of AnyEvent::XMPP::Component and the example
This extension allows to store and retrive avatars from vcards. On top of that it will also signal others that you support avatars and that they might have changed. See AnyEvent::XMPP::Ext::VCard.
You can send ping requests to other entities and also are able to reply to them. On top of that the AnyEvent::XMPP::Ext::Ping extension implements a connection timeout mechanism based on this.
Use the functions described above in the XEP-0082 item to decode the timestamps of delays.
<elmex at ta-sa.org>, JID:
<elmex at jabber.org>
Copyright 2007, 2008 Robin Redeker, all rights reserved.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.