Re: [ws-caf] WS-Eventing

["Mark Little" <mark.little@arjuna.com>]

Coordination by any other name.

According to some colleagues in IBM, the reason that WS-C wasn't leveraged
was that, unlike WS-CF, the a coordinator is only meant to be "fired" once
in its life (e.g., at the end of a transaction). Obviously not suitable for
something like event management. It's a shame though that they couldn't
leverage what's already there.

Mark.

----
Mark Little,
Chief Architect, Transactions,
Arjuna Technologies Ltd.

www.arjuna.com

----- Original Message -----
From: "Chiusano Joseph" <chiusano_joseph@bah.com>
To: "WS-CAF" <ws-caf@lists.oasis-open.org>
Sent: Thursday, January 08, 2004 6:46 PM
Subject: [ws-caf] WS-Eventing


> FYI - A new WS-* specification: "BEA, Microsoft, and Tibco Release Web
> Services Eventing (WS-Eventing) Specification [1]"
>
> Highlights:
>
> - The WS-Eventing specification "describes a protocol that allows Web
> services to subscribe to or accept subscriptions for event notification
> messages."
>
> - An example request to create a subscription for storm warnings is used
> to illustrate the notification protocol.
>
> - "Web services often want to receive messages when events occur in
> other services and applications. A mechanism for registering interest is
> needed because the set of Web services interested in receiving such
> messages is often unknown in advance or will change over time."
>
> - The specification intends to define a "means to create and delete
> event subscriptions, to define expiration for subscriptions, and to
> allow them to be renewed.
>
> - It defines how an event sink can determine which subscriptions it is
> receiving notifications for, and how one event sink can subscribe on
> behalf of another.
>
> - The specification is meant to leverage other Web service
> specifications for secure, reliable, transacted message delivery.
>
> Kind Regards,
> Joe Chiusano
> Booz | Allen | Hamilton
>
> [1] http://xml.coverpages.org/ni2004-01-07-a.html
>