![]() | |
![]() |
| | Thread Tools | Display Modes |
#21
| |||
| |||
|
|
"Tony Toews" <ttoews (AT) telusplanet (DOT) net> wrote in message news:vqet761qumrt466mhronnb545dskrhvb4l (AT) 4ax (DOT) com... On 1 Sep 2010 02:28:06 GMT, "David W. Fenton" NoEmail (AT) SeeSignature (DOT) invalid> wrote: too bad there isn't a simpler alternative to citrix / terminal services / RDP ? What's complex about WTS? It's really, really easy to set up, assuming you've got the hardware and bandwidth already in place. And you don't need much bandwidth either. While sluggish I've administered my web server via a 28.8 kpbs connection. That's mostly because WTS splits the screen into 16 'chunks', and only transmits the chunks that have changed. |
#22
| |||
| |||
|
|
"Tony Toews" <ttoews (AT) telusplanet (DOT) net> wrote in message news:0ant765po0c4h5uo7g5ce54tk88v1i22f6 (AT) 4ax (DOT) com... On Wed, 1 Sep 2010 23:36:30 +0100, "Stuart McCall" smccall (AT) myunrealbox (DOT) com> wrote: And you don't need much bandwidth either. While sluggish I've administered my web server via a 28.8 kpbs connection. That's mostly because WTS splits the screen into 16 'chunks', and only transmits the chunks that have changed. No, Terminal Services/RDP doesn't send down any graphics or chunks. Instead it sends down the UI rendering calls. I never mentioned it sending graphics data. But I remember reading sometime in the nineties I think, |
|
that the rendering info was tx'd in packets which represented one of the 16 chunks ('chunks' is my terminology - can't remember what MS called them). Of course I can't find anything to back up my claim (I googled for about 30 mins). If I find something I'll let you know, if you're interested. |
![]() |
| Thread Tools | |
| Display Modes | |
| |