RE: different message types handled by the same orchestration ?
- From: Ravi Shankar <shankycheil@xxxxxxxxxxxxxxxx>
- Date: Fri, 22 Jul 2005 07:19:01 -0700
Hi WenJun,
In case the application A sends a 101 it will discard the first 110 and only
act on the second 110 but the first 100 still needs to be responsed to...
Can a scenario be addressed using a sequential covoy pattern something like
this..
1. Receive Shape (attached to a port with filter for 100 & 101) triggers
orchestration
2. Move into a parallel shape
3a. One part of the parallel share is a another receive shape listening for
101 on the same receive location.
3b. The other part of the arm does the processing (ie: sending the message
to another application and waiting for a message from 110 (asynchronous send
& receive) and creation of a 110 to send to A
....
later both these arms condense into ajoin (OR)
after that we take a call if we did get A 110...
If we did not then EXIT else get the 110 sent previously, create another 110
with appropriate reference to the 101 & 110 sent previously and send it to A
and end orchestration.
--
Ravi Shankar
""WenJun Zhang[msft]"" wrote:
> Hi Ravi,
>
> My thought is Application A must be able to determine and drop the
> first time 110(if exists) after it sends 101, or it always accepts
> only 1 110 and ignore the other?
>
> Thanks.
>
> Best regards,
>
> WenJun Zhang
> Microsoft Online Partner Support
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
.
- Follow-Ups:
- RE: different message types handled by the same orchestration ?
- From: "WenJun Zhang[msft]"
- RE: different message types handled by the same orchestration ?
- References:
- different message types handled by the same orchestration ?
- From: Ravi Shankar
- RE: different message types handled by the same orchestration ?
- From: Stephen W. Thomas
- RE: different message types handled by the same orchestration ?
- From: Ravi Shankar
- RE: different message types handled by the same orchestration ?
- From: "WenJun Zhang[msft]"
- different message types handled by the same orchestration ?
- Prev by Date: More Info and progress on the same
- Next by Date: Custom Pipeline Component Config File?
- Previous by thread: RE: different message types handled by the same orchestration ?
- Next by thread: RE: different message types handled by the same orchestration ?
- Index(es):
Relevant Pages
|
Loading