Dave Meador wrote:
I wonder if you could solve the problem like this... First set the web page to refresh as quickly as possible, say every second. Then, when the browser requests an updated page, it gets the data very slowly. So it gets the first character just after sending its GET request. It gets the second character half a minute later, and so on. If this was done cleverly, it could stop the browser timing out, while avoiding sending anything real. When a message arrives, the process speeds up, repainting the screen with the new message in the appropriate place.How were you planning on solving the client-notification problem? I think there needs to be a client-side process running that maintains a connection to the sever... thus Java and Flash based solutions.
IMO port 443 is better, then proxy servers don't expect to be able to interpret the data stream.So why not provide a chat server that listens on port 80 and setup the client to connect to chat.domain.tld:80 and to all your...
--
Pete
_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
