W3C home > Mailing lists > Public > public-ws-resource-access@w3.org > January 2010

Re: issue 6435: v7 of the WS-Eventing state tables

From: Li, Li (Li) <lli5@avaya.com>
Date: Tue, 26 Jan 2010 14:57:35 -0500
Message-ID: <7DC6C0F0E8D7C74FB4E1E73CC371280A01505897@300813ANEX2.global.avaya.com>
To: <public-ws-resource-access@w3.org>
Cc: "Chou, Wu (Wu)" <wuchou@avaya.com>

Thanks for the update. After reading the tables and the notes, I wasn't
sure whose states we are describing. It appears that you are describing
the states of the processes, e.g. subscriber/sink or event
source/manager. However, this is difficult because each of these
processes can handle many subscriptions simultaneously. As the result,
the state tables have many empty cells that are undefined.

So what you did is actually defining the states of those processes
regarding one subscription. If this is the case, I think it is better to
directly define the state transitions for the subscription, instead of
the states of the processes. 

I think the information in the current tables can be reused.

This would lead to a more concise and precise description of the
behavior of the processes that developers care about.


Li Li
Received on Tuesday, 26 January 2010 19:58:07 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:34:54 UTC