adakin :   The build-in option is not implemented yet . We are working on these administrative functions . When this option be done , the messages would be archived for 1 year (configuratable in web.config).   Regards , Terry .

Hi  Juan :   Maybe the problem is that in the older version , the CuteChat cache the account list for performance , for 10 minutes .   So if a user registered , the CuteChat wound know him immediately.   We have changed that to 10 seconds in the newest version . We are planning upload it these days ...

Jim:   Thanks for posting the url for test.   I have found the problem .   It seems that the HttpRequest.Url.Host are pointing to 'emedsoft-75rkcl.emedsoft.com' .   I will fix this problem for you and upload new version tomorrow.   Regards , Terry .

Jim:   I think that is known bug in Asp.Net 1.0/1.1 To resolve this problem , the ASP.NET must re-copy the 'shadow assemblies' , there are some ways :   A. iisreset B. re-copy the dll into the bin C. create a new file in the bin folder , and modify it and save it .   Regards , Terry .

Hi , jimcio :   There are two connection strings in the web.config :   1. appSettings\@ConnectionString1 = ...   2. cuteChat\@ConnectionString = ...   Did you modify the cuteChat\@ConnectionString same as the ConnectionString1 ?  

Hi ance :   The CuteChat do not use the System.Net and the Socket to exchange informations between clients and server .   In browser , CuteChat use the 'MSXML2.XMLHttp' to send a request to server , and download results from server.   The data transfer between client and server are text based.   About the threading ...

For the   >>( Because the pushing need a live network connection , and it really waste the network resource and server resources )   It means HTTP pushing for Web servers , would waste HTTP connections and the Asp.Net resources.  

Hi , MarkWil  :   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 ...

dimitrisv :   CuteChat have its own protocal . It's not compatible with mIRC .   Regards , Terry .

Hi GWBasic   When you test the CuteChatSample , please ensure the <providers defaultProvider=''Sample''> , ensure the defaultProvider is 'Sample' .   Sometimes we test the web.config for SharePoint , and forgot to change the defaultProvider back..   You should change the ConnectionString too .   Regards , Terry .