W3C home > Mailing lists > Public > public-ws-chor@w3.org > August 2003

RE: [ws-chor] 7/28/2003: Reqts 1.0 Comments

From: Yaron Goland <ygoland@bea.com>
Date: Tue, 19 Aug 2003 12:22:25 -0700
To: <jdart@tibco.com>
Cc: <public-ws-chor@w3.org>
Message-ID: <00c701c36687$39943c20$12cccf0c@bea.com>

Which requirement do you think would necessitate this? More importantly,
what is the use case behind that requirement?
	Thanks,
		Yaron

> -----Original Message-----
> From: public-ws-chor-request@w3.org
> [mailto:public-ws-chor-request@w3.org]On Behalf Of Jon Dart
> Sent: Thursday, August 14, 2003 11:12 AM
> To: ygoland@bea.com
> Cc: public-ws-chor@w3.org
> Subject: Re: [ws-chor] 7/28/2003: Reqts 1.0 Comments
>
>
>
> Yaron Goland wrote:
>
> > Where I think the real confusion is coming is from the term
> 'control logic'.
> > What I specifically mean is that when a web service has an
> option for which
> > message it can send next then the logic the web service
> uses to choose must
> > not be expressed in the choreography definition.
>
> What about something like an iteration facility (which is a
> very simple
> example of control logic, IMO). If the iteration count is <
> 3, you send
> a message, otherwise you don't. I think this is probably
> necessary given
> the other requirements.
>
> --Jon
>
>
>
Received on Friday, 22 August 2003 02:59:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 01:00:27 GMT