Thanks for downloading and testing the demo , And thanks for your compiments .

 

The CuteChat use the HTTP protocol to exchange information between server and client . But it does not use server push technology . ( Because the pushing need a live network connection , and it really waste the network resource and server resources )

 

The CuteChat access the server for interval time (configuratable) . Each time the CuteChat client (scripting) send or get messages , the client would use the HTTP protocal to send a request to the server , and the server would return immediately after the request have done .

 

So , if anything HTTP could do , the CuteChat could do too. So if a user could access a website through firewall/proxy , the user could access CuteChat on that website too .

 

The CuteChat support any Port as HTTP does.

 

--> Of a Server with P4 2.0G CPU <-- :

Currently We just test the CuteChat with 20 persons in it , it have no any problem and the Usage of CPU is only 10% . So I believe that the CuteChat can support 200 persons at the same time . And the maximun number of users should be much more then 200 , maybe the messages would be updated slower , but the CuteChat would not crashed .  (I means if 1000 people are online , the Server would be OK , and the only result is the messages would be updated more slowly , about for every 10 seconds)

 

Regards , Terry .