Posted by Jim Guerber on September 08, 2006 at 12:15:32:
In Reply to: Comet as a service posted by Doug Pegg on September 04, 2006 at 17:16:07:
We cringe when we hear "Citrix". It is difficult to get our minds around what is happening here.
The citrix machine is a multi user windows machine -- that is where each user is actually running windows. The citrix client machines just express the screen generated from the citrix host and handle transfer of keystrokes and keyboard to the host. SO, the CometAnywhere client is located in the citrix machine.
The question is just where the Comet host should be located. Comet as a service needs to have the file system installed as a service on the same machine. This machine is where all comet programs will run, so it probably should not be the same machine as the citrix machine for performance.
So, I would suggest that the main file server reside on machine #1. Comet (the CometAnywhere host), reside on machine #2 (install Cometserve32 as a service on this machine as well). Machine #3 should be the citrix host (CometAnywhere client).
Now, If the screens seem slow, duplicate the citrix boxes. If the programs seem to run slow, duplicate the comet machines, and if the file access seems slow, beef up the server machine.
By the way, the reason to install CometServe32 on the Comet Host machine is for access to the temp directory (and any other folders you want local to the user and not shared).
You may get away with combining Machine #1 and Machine #2. You definitely want to avoid having multiple Comets running on the same machine, as opposed to CometAnywhere clients (I don't know how to accomplish this on a citrix host).