Feridian supports approximately 90-95% of the XMPP specs.
XMPP Features
- TLS – provides secure packet and authentication exchanges
- SASL – DIGEST-MD5 and PLAIN are currently supported.
- Jabber style authentication support for backwards-compatibility (ie. 0k, digest, plain authentications)
- Full Stream features parsing and support for XMPP specs.
- Resource Binding stream
- Session stream
- Sending packets synchronously and asynchronously
- Receiving incoming stanza packets. Unknown packets (packets that cannot be unmarshalled by Feridian) will be reported so that user can implement support or optionally ignore it. Feridian follows XMPP specs by ignoring unknown stanzas.
- IQ Roster, as per XMPP specs
- IQ Privacy, as per XMPP specs
- Full xml:lang and localization support
JEPs Supported
Extreme Customization Capabilities
Feridian API also takes ease of supporting custom packets and stream features to a whole new level:
- XML-style configuration files makes for easy configurability of Feridian
- Easy way to override default handlers without changing any Feridian jar files
- Modularity allows you to add custom packets and stream features support without having to modify any code or subclass any Feridian classes. Simply implement the appropriate interfaces if required and write a XML configuration file to notify Feridian of the new capability.
- Feridian allows you to take complete control over the entire stream processing if needed. This is most useful for stream processing during handshake negotiation such as adding in the ability to support stream compression.
- Feridian uses JiBX as the underlying XML parsing mechanism. What this means is that you can add support for custom XML packets by writing a binding file instead of xml marshalling/unmarshalling code. If custom marshalling/unmarshalling code is required, the option is available as well. Visit http://jibx.sourceforge.net/ to see how JiBX works.
