Question

Helo,

I have implemented a chat application using Comet.
the request is “hang” on the server until new messages arive.
It, then, returns to the client with the new messages, and goes to the server again.

My problem is:

In order to check for new messages, I poll the database every 600 ms.
I perform a simple query “select…from messages where messageId > ‘ + lastMessageId.

In addition, in order to maintain presence, I update the database very (very) often
with each user “LastKeepAliveTime”.

The SQL Server transaction log is growing huge, and, at a certain point, my chat application stops working.

The chat users are not registered users, they are just random users who can leave the page at any time.

thanks
Yaron

Answer 1

Could you use a common cache object for the last keep alive information? It seems like its a small amount of information and you could avoid a lot of sql updates.