OK, thanks.=20 Actually, there's no problem uploading messages at the same time, = because the smaller period between messages is a couple of minutes. The problem happens when the client first connects to muscled, because = it receives the buffer of all sent messages and my app needs to receive = the full history... Regards, Dario -----Original Message----- From: muscle-bounce@xxxxxxxxxxxxx [mailto:muscle-bounce@xxxxxxxxxxxxx]On Behalf Of Jeremy Friesner Sent: Jueves, 26 de Agosto de 2004 12:18 p.m. To: muscle@xxxxxxxxxxxxx Subject: [muscle] Re: Question about the collection that holds the messages > and sure, I could do that. What I'm wondering is if there's some way = to =3D3D > avoid the repetition problem, maybe using a simple queue, but without = =3D3D > recompiling muscled... If you have multiple Messages to upload at the same time, you could AddMessage() them all into a single Message, and then just upload that = one Message using a unique node label -- that would cut down on the overhead somewhat. (To save space further, you could run the Message through DeflateMessage() before uploading it, so that the data is stored in = zlib-compressed format on the server) However, there is no built-in way to append to a FIFO queue of Messages = in=20 the server database, AFAIK, so you would have to modify muscled if you=20 wanted that. -Jeremy