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 947 - CDL does not contain any mechanisms to detect whether a timeout actually occurred or not
Summary: CDL does not contain any mechanisms to detect whether a timeout actually occu...
Status: RESOLVED FIXED
Alias: None
Product: WS Choreography
Classification: Unclassified
Component: Spec: Structural (show other bugs)
Version: unspecified
Hardware: Other other
: P2 normal
Target Milestone: --
Assignee: Martin Chapman
QA Contact:
URL: http://lists.w3.org/Archives/Public/p...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-17 13:50 UTC by Greg Ritzinger
Modified: 2005-01-04 20:51 UTC (History)
0 users

See Also:

Attachments

Description Greg Ritzinger 2004-11-17 13:50:23 UTC 
Earlier in the year we adopted both deadline and duration timeouts on interacts. Unfortunately CDL does not contain any mechanisms to detect whether a timeout actually occurred or not! Attached is a proposal that fixes this. 

Martin.

Proposal:
http://lists.w3.org/Archives/Public/www-archive/2004Nov/att-0025/Timeout_exception.pdf
Comment 1 Greg Ritzinger 2004-11-17 13:51:17 UTC 
Couple of issues/questions:

1) the syntax has the 'time-to-complete' attribute where it should say 
'deadline'

2) why this restriction?
 At most one record element MAY be specified where the when attribute is 
set to "timeout" for fromRole and toRole respectively"

shouldn't the record reference fields support a list of names, as in the 
exchange element?

Regards
Gary

http://lists.w3.org/Archives/Public/public-ws-chor/2004Nov/0065.html