09-28-04 10:52 PM
I think I read somewhere that the default batching is of 5 messages for the
FILE Adapter, but iI might be wrong. You could write your custom adapter,
that closes the file stream explicitly. But even then what you are trying is
very indeterministic. How long are you going to put the delay for? What
happens if the file is too big and the delay is not enough? Or too small and
you wind up wasting time?
What Matt Milner has suggested would be the cleanest way to achieve your
goal, and it is NOT a workaround. I think you are not taking into account,
the fact that the architecture is based on a pub-sub mechanism (in your case
the Orch is the pub and the send port is the sub, and both are separate
entities), and is not plain vanilla sequential execution. Hence the reverse
direction communication using DeliveryNotifications(and ACK/NACK) is
available.
Also, you are supposed to put your Send SHAPE inside a synchronized scope,
not a send port. The second requirement is that the send port should have
DeliveryNotification set to Transmitted.
Hope that helps
Regards
Dev
"aaagent" <agent@nospam.com> wrote in message
news:umbdvxYpEHA.3572@TK2MSFTNGP10.phx.gbl...
> ok how do i negate this batching mechanism
>
>
> "Devdutt Patnaik" <aquarius@taurus.com> wrote in message
> news:%23HHghIXpEHA.3252@TK2MSFTNGP14.phx.gbl...
> than
> message
> property
> works
put[vbcol=seagreen]
right.[vbcol=seagreen]
complete[vbcol=seagreen]
finally[vbcol=seagreen]
> returns
>
>
[ Post a follow-up to this message ]
|