Programming Jabber

Further Ideas

There’s only so much that can be included in a demonstration script. There’s plenty of room for improvement, even if you don’t count rewriting it all from scratch. For example, you could store registrations in a SQL database or, alternatively, use the Jabber server’s own xdb component. More importantly, a static list of RSS sources is rather restrictive. How about allowing the user to register their own URLs? Or building an administrative mode that accepts a special IQ from certain JIDs, with which the RSS source list can be maintained?

The browsing response function would be an ideal candidate to be expanded upon. Another level of browsing could be added that would return browse items that reflect the specific user’s RSS source registrations. It’s probably worth exploring the power of addressing the component to include the RSS source, to extend the interactive facilities. For example, you might want to have the script accept and act upon messages sent to the component’s JID, which includes a username portion representing the RSS source.