Areas for future development

This is a preliminary, very incomplete list of possible future developments. A description should contain at least: what the feature is about, in what space it would have to be implemented (core, extension, remote application), and pointers to more information.

File transfer using libjingle

"The Libjingle library aims to create high quality peer-to-peer sessions over a wide number of network configurations, including firewalls and Network Address Translation (NAT)" (http://code.google.com/apis/talk/about.html)

It should be possible to implement this as an extension, without modifications to xmpp4moz. Possible approaches:

• wrapping libjingle in an XPCOM component;
• customizing the pcp example from libjingle and driving it through inter-process communication;
• adapting jinglepipe.

Resources and similar projects:

• libjingle home;
• XEP:0166
• Jingle file transfer for Psi.

SASL authentication

Currently, only non-SASL authentication is supported. XMPP specifications require support of SASL.

The high-level API implementation (chrome/content/service/jsapi.js) has to be modified. Core services (chrome/content/service/{client_service,client_session}.js) will probably need modifications as a consequence.

Resources:

• RFC3920, Section on the use of SASL
• RFC4422

Notifier enhancements

JabBiff could be improved by e.g.:

• notification methods other than desktop popups (such as sound);
• notification of event types other than presence (such as messages);
• granular control over notification (e.g. different sounds for different contacts).

All can be done in extension space.