[muscle] Re: Question about the collection that holds the messages

Thanks for your answer,

and sure, I could do that. What I'm wondering is if there's some way to =
avoid the repetition problem, maybe using a simple queue, but without =
recompiling muscled...

Dario

-----Original Message-----
From: muscle-bounce@xxxxxxxxxxxxx [mailto:muscle-bounce@xxxxxxxxxxxxx]On
Behalf Of Jeremy Friesner
Sent: Jueves, 26 de Agosto de 2004 11:29 a.m.
To: muscle@xxxxxxxxxxxxx
Subject: [muscle] Re: Question about the collection that holds the
messages


> What I'm doing right now is inserting the date in milliseconds in the =
=3D3D
> middle of the message, to avoid repetition:
>=20
> 150.100.104.191/3/ROOT=3D5FNODE/103689823465/SOME=3D5FNODE
>=20
> I don't know if this is the best solution for the problem, or if =
there's =3D3D
> a more elegant way.

How about having each client keep an integer counter, and increment the =
counter before each Message it uploads=3D3F  Use the counter value =
instead of the time-in-milliseconds.  That way you are guaranteed a =
unique node name, even if two Messages are sent within the same =
millisecond.

-Jeremy

Other related posts: