On Mon, 1 Dec 2003 08:26:10 -0800, "jimmyBoy"
<anonymous@discussions.microsoft.com> wrote:

You have allready received one solution. To me, however, that
solutions does not seem to guarantee a sequence.

Having only one receive function look at a MSMQ does not guarantee
anything, because you can have more than one thread that picks up
messages.

Anyway, depending on the scanario, here is another solution; The
program that outputs the document also writes a line in a database
with the timestamp and some sort of identifier for the message. Then,
let all messages be delivered to an AIC that check the msssages in the
database to make sure that all previous messages have been delivered.
If not, hold the message and wait.

This requires that only one can write to the database at a time..

Good luck

>Folks
>
>One of the requirements we have, is that the messages which are emitted in 
realtime
>from the source application, should reach the target application in the SAM
E sequence.
>
>Considering that BTS does not guarantee sequencing of messages, and also co
nsidering
>that we might have a multiple BTS server (hardware) scenario, what options 
do I have to
>ensure sequencing of messages is maintained ?
>
>I am assuming that I will have to build some mechanism for doing this, outs
ide of BTS,
>maybe dotNet components, etc and am open to such ideas as well...
>
>thanks in advance
>
>cheers
>

--
Jan Eliasen, representing himself and not the company he works for

[ Post a follow-up to this message ]