As reported several times we hat a lot of problems with Cute Messenger 30/31. Some background: We integrated the CuteChat buddy list in a frame on the entry page of our application. The buddy list is shown all the time. We could observe the following issues (beside the known bugs, which are mostly fixed in 31):

1. When the browser was left open the memory usage of the IE went up and up, until IE used up to 1GB of memory. The whole application (client side) became instable then.
2. With CuteChat 3.1, after the third click on a buddy (to open the message window) the client side browser hanged.
3. When waiting for a while and then reloading the whole page (also reloading the CuteChat buddy list) strange exceptions occurred.

We tried hard to find out what the problem could be. Today we found a possible candidate – HTTPCompression. We had setup a new website with our application, without enabling HTTPCompression. There we did not observe the above issues. However more testing is needed. For the moment we have enabled HTTPCompression for our application, but disabled it for the CuteSoft_Client folder. This seems to work.

Can you tell us why CuteChat is now working with HTTPCompression enabled? Are there any specific issues? As I said we still need to test more, but disabling HTTPCompression has definitely improved things for us.