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 3106 - Channel Passing
Summary: Channel Passing
Status: RESOLVED REMIND
Alias: None
Product: WS Choreography
Classification: Unclassified
Component: Implementation/CR Issue (show other bugs)
Version: unspecified
Hardware: PC Windows 2000
: P2 normal
Target Milestone: --
Assignee: Martin Chapman
QA Contact: WS Choreography mailing-list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-11 13:23 UTC by Martin Chapman
Modified: 2006-08-01 21:20 UTC (History)
0 users

See Also:


Attachments

Description Martin Chapman 2006-04-11 13:23:19 UTC
Implementation issue from Gary:

. Business messages can be correlated to a channel instance and
choreography session using identity information derived (through
the use of token locators) from the message contents
.  However, channels passed over other channel instances do not
carry any business information, and therefore how can they be
correlated?
.  Approach taken in pi4soa is currently restricted to use of WSAddressing
endpoint reference, which it stores the identity token
values of the channel on which the exchange is occurring 
however this is not interoperable, as it relies on prior knowledge
of the identity token encoding within the endpoint reference

. Channel passing is also restrictive, as it can only be passed within
its own exchange
. This is currently necessary to enable the formal verification to
identify where the channels are being passed

. However, for subsequent versions of CDL, we should investigate
the ability to describe message exchanges where a channel's
details are passed as part of a business message, but still remain
explicit enough for formal verification.
Comment 1 Martin Chapman 2006-08-01 21:20:40 UTC
at meeting on 1st august 2006 it was accpeted to defer this issue to version 2, since a workaround exists. Marked this as resolved, remind.