I don't know if this has been discussed anywhere else.
I try to run rdesktop over OpenSSH with compression over a crummy DSL line at
100Kb/sec (bits not Bytes that would be 100KB/sec with a capital "B".) It
works but I can see that rdesktop is sending tons of small packets while
starting up which has to be inefficient. Startup take a long time.
One of the great problems with networks is that they send data in bigger chunks
more efficiently but if you are using a networked GUI you don't want to wait a
long time for the pointer to move a little if you move the mouse a little so
you send data in small, inefficient packets rather than wait for enough data to
build up so that you can send one efficiently.
Startup is all different. Nobody is expecting user interaction at startup.
One possible solutions is that if you could configure the use of large packets
for an amount of time after startup and then switch to small packets it would
work better. The end user would have to pick the amount of time to add to a
run-time configuration option like a command-line option or a configuration
file that could select for options on a per-host basis so that hosts configured
on a fast network would not be messed with in order to improve the
configuration for a host connected on a slow network.
How does this sound? Does anyone have a better idea? I haven't spent very
much time thinking about this problem.
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
Get latest updates about Open Source Projects, Conferences and News.