RE: 'Catch' review Re: [tamie] Minutes F2F Korea in wiki, + reminder meeting Tuesday 01/06

["Durand, Jacques R." <JDurand@us.fujitsu.com>]

Stephen: <JD>

-----Original Message-----
From: stephengreenubl@gmail.com [mailto:stephengreenubl@gmail.com] On Behalf Of Stephen Green
Sent: Monday, January 05, 2009 5:39 AM
To: Durand, Jacques R.
Cc: tamie@lists.oasis-open.org
Subject: 'Catch' review Re: [tamie] Minutes F2F Korea in wiki, + reminder meeting Tuesday 01/06

A. The 'catch':

In general when considering virtual time, etc, it does seem to get a little complex Maybe a simple intro would be to just consider three ways to catch:


1. duration = 0    - inside a loop

<JD> not necessarily: if I know that my event MUST be there at the time my script is doing <catch(dur=0)>  then why would I need a "loop" around? I may want my <catch> to fail right away in case the expected event is not there.

2. duration <> 0 or between two times (or virtual times)   - typically
not inside a loop

<JD> Right. Here the <catch> would "wait" as long as needed, acting as a synchronization mechanism (not just as a query as in (1)).

3. as one or either of the above (?) but with a macro e.g. 'catcher'

Then we might list the pros and cons of each of the above. Maybe this is where we start with the tutorial documentation of catch/catcher.

B. The 'catcher':
Here a catch is working with a catcher: there seems to be redundancy/duplication of parameters (both in catch and catcher)

If I refer to a catcher in a catch, why do I still need anything else in the catch? I would have thought the catcher would include the details (a bit like a specialized subroutine) so that all I need to say in the catch is <catch catcher='xyz'/> (comparable to xslt's  <call-template name='xyz'/>) .

<JD> Yes, it appears that if we want to define a "reusable" catch statement, we have now the "function" construct for doing that, no need for defining a special "catcher" construct. This function would be parameterized, and so will the <catch> inside (i.e. use these parameters). So if we want to invoke such a <catch>, we just invoke instead the wrapping  function, e.g. from inside a variable declaration.

Best regards

Steve


2009/1/5 Durand, Jacques R. <JDurand@us.fujitsu.com>:
> For review:
>
> http://wiki.oasis-open.org/tamie/2008-12-11%2B12Minutes
>
> also note the action items:
>
>
> AI-Dec08-1: Jacques: script Use Case #1 based on latest script
> language design.
>
> AI-Dec08-2: Dale: make proposal for Use Case #3, a business
> transaction with Cancel Order and non-deterministic flow.
>
> AI-Dec08-3: Cho and KIEC to provide more input on desired event
> structure, and use cases for using more than one Event Board.
>
> AI-Dec08-4: Stephen: review and comment on the CATCH operator,
> especially some patterns emulating XOR behavior and timing control.
>
>
>
> see meeting agenda for Tuesday:
>
> http://www.oasis-open.org/apps/org/workgroup/tamie/event.php?event_id=
> 21815
>
>
>
> Jacques



--
Stephen D. Green

Document Engineering Services Ltd



http://www.biblegateway.com/passage/?search=matthew+22:37 .. and voice