Motility (Pun Intended)

RSS Notification Registration Service Specs - or so I think

This describes how RSS notifications are sent/how aggregators register for notifications.

I am slightly confused, but here are my thoughts:



This is telling the aggregator to send an XML-RPC message to radio.xmlstoragesystem.com on port 80, with path /RPC2 to the procedure named xmlStorageSystem.rssPleaseNotify to request notification.
-The aggregator is the process that collects updates from RSS feeds

A workstation calls the cloud to register. The procedure takes five parameters: the name of the procedure that the cloud should call to notify the workstation of changes, the TCP port the workstation is listening on, the path to its responder, a string indicating which protocol to use (xml-rpc or soap, case-sensitive), and a list of urls of RSS files to be watched. The cloud can determine the IP address of the caller from the request.
-This seems the opposite of the last para. I guess an aggregator would identify its port, IP, path and protocol info to the cloud (mentioned in the earlier para) to get notifications.

When a subscribed-to channel changes, the cloud calls back to the procedure named in the registration call with one parameter, the url of the channel that changed. At that point the workstation could read the channel, or notify other workstations that the channel has changed, clear a cache, send an email or do nothing.

-Somehow this makes me think that a workstation is an intermeiary between the channel and the registrants that sends out notifications?!?!?!

Now I am truly confused.

posted by Anwar @ 12:39 PM