HTTP-based Notification system
By Bruno Harbulot on Wednesday, July 25 2007, 14:10 - Permalink
Event notification is something quite often required or at least useful in distributed applications.
After my experiences with WSRF, I tried to design a more "RESTful" approach to notification in our application. I've written a draft of an HTTP-based Notification system and, although I admit this draft is incomplete and could be substantially improved, the main principles I've described there work in our application.
In short, it mimics the SMTP protocol at the application level and models mailboxes and messages as resources. Sending something like this via an HTTP POST to a destination URI works fine:
<Message>
<From href="uri-of-the-sender" />
<To href="uri-of-the-recipient" />
<Content>
<ns1:test>any XML you want</ns1:test>
</Content>
</Message>
The idea with this is to be able to support both the pull and the push approach. The pull approach could be implemented using an Atom feed.
It's all well and nice in an application that I can control entirely (clients and servers), but there's obviously a problem when trying to make this inter-operate with other systems. Two specifications thus come to mind:
- the WS-Notification (OASIS) standard and
- the Atom Publishing Protocol.
I've started to look at them, and I'll write more about this in further entries.








Comments
The other possibility is to use XMPP/Jabber http://www.jabber.org/
Just to add "Using IM for Grid computing", http://www.dehora.net/journal/2006/...
Thanks for the pointers. XMPP is indeed a good candidate for this type of application. HTTP and XMPP could certainly be combined if required, as mentioned in BOSH (or perhaps differently, as Mark Baker suggested a few weeks ago on his blog).