I guess this approach doesn't have much overload comparing to the time taken by transactions. I have been using this techinique for sending about 30 SMSs a second.
Trustin
2005/7/20, Alex Burmester <[EMAIL PROTECTED]>:
My server has to keep incomming connections open to a third party
and route multiple messages over the same channel using transaction ids
to keep track of which messages are outstanding. I need a way to time out
these transactions. Currently every half second I scan my outstanding
message queues and remove any messages that are older than the timeout. My
issue with this is that the cleanup method has to lock the whole complex
datastructure of connections and outstanding messages during the scan.
Doesn't seem to be a problem yet but I'm concerned that under higher load it
will become the main bottleneck. I was thinking about putting in an event
queue and firing timeout events for each message but I'm not sure if the overhead
of registering and deregistering each timeout event for each successful
message is worth it. Just wondering if there is a pattern that I'm not
thinking of that gets around these issues.
Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/
