Thanks Mardy--that's exactly the 'space'I thought CTXS was/is occupying. Problem being that a guy who really knows the technical end could blow in here and tell me I'm off in left field (I still marvel at e-mail).
My interest in CTXS began when we implemented a VPN for our small company--basically linking a mid-West office with our Northern CA headquarters. The NorCal server hosts a fairly large application which we want the Denver folks to utilize, via the internet. The problem, of course, is that the net gets clogged up at unpredictable times and even with DSL at either end, the "cloud" is the cloud is the cloud, if you catch my drift, meaning that screen draws and response times can get very ifffy.
Short of a, prohibitively expensive, T-1 line, an alternative is Microsoft Terminal Server which, according to my VERY LIMITED UNDERSTANDING, basically cuts down big time on the amount of data that needs to get "shipped" back and forth between the server and the remote client, thus creating an acceptable level of responsiveness ALMOST independent of whatever transmission speeds the internet happens to be in a mood to provide on any given day. [having written this, I can almost feel the technical flames coming my way for what is doubtless a butchered explanation of Terminal Server]
Anyway, plunging on, I then was told that MSFT got this handy, dandy little miracle-worker from a company called CTXS. Having seen at first hand how effective it is, I thought . . . . .
I will now retire and await a sure and certain death at the hands of people who, unlike me, know what they're talking about. Best, Mike Doyle |
