[ rdesktop-Bugs-3012065 ] mouse movement events consume excessive bandwidth

Bugs item #3012065, was opened at 2010-06-06 09:13
Message generated for change (Tracker Item Submitted) made by fermulator
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=381347&aid=3012065&group_id=24366

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Mouse Input
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Fermulator (fermulator)
Assigned to: Nobody/Anonymous (nobody)
Summary: mouse movement events consume excessive bandwidth

Initial Comment:
As per some discussions on the [email protected] e-mail list, it has been confirmed that when we enable "mouse motion events" (default), rdesktop consumes an absurd amount of upload bandwidth.  The Windows "mstsc" RDP client does not have this poor behaviour, and the following summary outlined by "J.S." helps us understand why, and what can be done to improve rdesktop.

Summary:
------------------------------------
-------- Original Message --------
From: J** S*** <**********>
Sent: Sun 06 Jun 2010 04:23:11 AM EDT
To: [email protected]
Cc:
Subject: Re: [rdesktop-users] rdesktop mouse movement events consume
excessive bandwidth

>From my experience as an RDP developer, I think I can explain the
difference between rdesktop and MSTSC on input.

rdesktop is less efficient for 3 reasons.

1. input PDUs have a "number of events" field, see rdp_send_input in
rdp.c.  rdesktop always sends one at a time.  MSTSC sometimes sends
many.

2. Nagle algorithm.  rdesktop always disables the nagle algorithm.
This make for faster response time but more bandwidth.  Not sure but I
don't think MSTSC ever disables this.

3. Fast path input.  Since RDP 5 there is a more compact PDU for input
that rdesktop does not utilize.  I implemented this in freerdp but not
rdesktop yet.

Changing 1 is difficult but 2 and 3 are fairly easy.
For 1 you need some kind of thread or timer.

J**
------------------------------------

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=381347&aid=3012065&group_id=24366

------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo