Posted by Jim Guerber on June 27, 2007 at 01:23:57:
In Reply to: Comet in a Terminal Server environment posted by Brian Manwaring on June 22, 2007 at 17:37:23:
Terminal server is a derivative of Citrix, and we have several installations using that. I have tried Comet in a terminal server environment in a limited way, and it seems to work. I say "seems" because, in the past, we have encountered many problems with these environments.
The problem stems from the issue of CometServe distinguishing between one Comet node and another. At one time, we used the IP address to decide which node we were talking to. In a terminal server environment, each user still has the same IP address. Then we tried using the combination of IP address and TCP port number. We found cases where windows would fool around with port numbers, disconnecting and reconnecting them, making this technique unusable. Current Comet releases rely on a sort of "cookie" that is generated at login time and passed back and forth with each packet. The "cookie" has nothing to do with ip address or port number.
The safest advice we can give you is to use CometAnywhere. Run a CometAnywhere host on the same machine as CometServe. On the terminal service host, make each user a CometAnywhere client. This has ALWAYS worked. CometAnywhere performs GREAT on a local area network.
In any case, send us your ini files and we can help you configure your installation. Let us know how it works out.
Good luck
Jim