This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 668 - The granularity at which isAligned() can be used is too big
Summary: The granularity at which isAligned() can be used is too big
Status: RESOLVED WONTFIX
Alias: None
Product: WS Choreography
Classification: Unclassified
Component: Spec: Coord and alignment (show other bugs)
Version: unspecified
Hardware: Other other
: P2 normal
Target Milestone: --
Assignee: Greg Ritzinger
QA Contact:
URL: http://lists.w3.org/Archives/Public/p...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-13 10:38 UTC by Greg Ritzinger
Modified: 2004-10-05 19:50 UTC (History)
0 users

See Also:


Attachments

Description Greg Ritzinger 2004-04-13 10:38:05 UTC
A comment with respect to state alignment and work unit. It looks like
the granularity at which isAligned() can be used is too big and that
could defeat the purpose of work units along with state alignment which
are otherwise very useful concepts. BPSS offers alignment at the message
level (it is not because you received a message that this message is
understood as valid and can be processed by the receiver). If no
protocol is available to notify the sender of potential standard errors
for each message, then these error notifications must be implemented in
the choreography itself. This is not a satisfying solution, because you
end up acking the ack. As I learned it, it is only through the use of
widely agreed upon and structurally constant signals that you can really
guarantee state alignment otherwise, I am under the impression that it
will remain a wish rather than a fact.