Events and WebServices

My notes from a very quick look at WS-Notifications / WS-Eventing. There are two specs for doing pretty much the same thing. You have something that produces events, for example with a light switch, the events might be light switched on, light switched off. With these specs other systems like the coffee maker (consumers) can register with the producer to receive events when something happens. An example use might be that when the coffee machine starts up it registers with the light switch to receive "on" events. Then when the light switch it turned on it sends an "on" event to the coffee machine so it brews some coffee. The light switch and the coffee machine would have to agree on a message format but the specs define how the registration works and what the outline of the events looks like. The producer looks after the list of consumers that want to be notified of events and when registration happens the consumer tells the producer where events should be sent to. Neither of these specs specify anything about what is in the contents of the notifications. They are similar to event listeners from the Java GUI world. Both the specs came out around 2004:

• - WS-Notifications is the IBM spec (support for brokers, liked to WS-Topics/WS-Resource, more Java focus?, links to Grid? ). http://ifr.sap.com/ws-notification/ws-notification.pdf
• - WS-Eventing is the BEA/Microsoft spec (small/simple). http://ftpna2.bea.com/pub/downloads/WS-Eventing.pdf