According to the support forum there seem to appear quite serious performance issues when some 20+ people are using the chat simultanously.

So maybe we can help to solve those issues on our end. But for this we should need to have a deeper understanding of your module's high-level architecture.

For instance:

a) Does you chat-module poll the DNN application regularely or does the Ajax Client get only notfied when new messages are available ?
Yes, the chat-module poss regulary (ever 1.5 seconds)... there is really no other way to know if there are new messages available or not.

b) Are all the messages exchanged between server and client or just the new ones ?
Just new messages are exchanged.  During polling, the client asks for JUST new messages.

c) is the server freed from resources taken from chat-users that have left ?
Yes, when users leave the chatroom, they are removed from all cached resources.

d) what kind of caching are you using and how can we configure this ?
We are using the native DNN Caching Provider

e) what is cached ?
In Swirlchat versino 1.x ALL resources (users,messages,GUIDs, etc) are cached.  In version 2.x (which we are in development now) only GUIDS are cached.  All other resources are in the DB, and retrieved upon demand only.

etc.

Would really help to put a draft document together as a basis for discussion as it makes not much sense to purchase and dig into the code without having understood the big picuture.

kind regards

Karin