W3C home > Mailing lists > Public > www-ws-desc@w3.org > December 2003

Fulfillment of action item: proposed descriptive text for patterns

From: Amelia A Lewis <alewis@tibco.com>
Date: Fri, 05 Dec 2003 13:52:18 -0500
To: WS Description List <www-ws-desc@w3.org>
Message-id: <20031205135218.3a4c08a1.alewis@tibco.com>

In fulfillment of the action item:

Tibco\Amy to draft sample scenarios for MEPs

from 13 November, the following texts are proposed (numbered per the
editors' draft, which is currently slightly out of synch with the HTML
version--skip over the "multi"s to get the numbers right if looking at
the HTML).  I suggest that this text be placed, for each pattern, in a
paragraph following the current paragraph containing the definition of
the {pattern} property.

3.1 In-Only
This pattern is commonly used for reporting, logging, or transmitting
commands, when it is possible to monitor errors out of band or error
reporting is not considered useful.

3.2 Robust In-Only
This pattern is commonly used in the same situations as the In-Only
pattern, but includes facilities for in-band reporting of errors.

3.3 In-Out
This pattern is the classic request/response commonly found in
client/server computing, and often reproduced in other networking
paradigms.  It is the base pattern used for RPC styles.  Several
variants are possible; this one only permits two participants, and
requires the response message.

3.4 Out-Only
This pattern is encountered as a "notification" or "event", where the
service either has out-of-band channels for error-reporting, or error
reporting is not considered useful.

3.5 Robust Out-Only
This pattern is used in the same situations as Out-Only, but provides an
in-band channel for error-reporting.  It is very commonly encountered in
messaging and publish/subscribe systems.

3.6 Out-In
This pattern may be used in service-to-service interactions, or in
networking paradigms in which the participant other than the service has
a fixed address, and the service is the expected initiator.

3.7 Out-Optional-In
This pattern may be encountered as a discovery mechanism in multicast or
broadcast use, or more generally for networking protocols in which the
service is expected to initiate interactions (such as
publish/subscribe).

Amy!
-- 
Amelia A. Lewis
Architect, TIBCO/Extensibility, Inc.
alewis@tibco.com
Received on Friday, 5 December 2003 13:52:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:27 GMT