The customer would like to have Mouse Motion tracking turned off in their Swing application for example when moving the mouse across the window - this would require turning off the mouseMotionListener in the JVM AWT/JSwing classes in the JVM. As it is uncertain to the consequences once this listener has been turned off (i.e. through an -XX jvm startup parameter), mouseOver and other similar listeners may not work appropriately or at all - this is acceptable to the customer.

Please refer to the attached MS Word document from the customer for the application architecture. When the UI was XView based, the above deployment worked well for customers working over a 128 kbps link. When the customer migrated to the new release of the 5620 which uses the Java UI they finds the UI unusable.

IP packets carrying X windows data between the JVM and the X Server had increased 2 orders of magnitude to get a window into focus. Mouse movement traffic has increased 4 orders of magnitude even when there are no listeners registered. Button press traffic has increased 2 orders of magnitude.

XS-J.tar: This archive contains a XView based program and a Java program including source.

networkTrafficData.tar: It contains network traffic data when a window comes into focus and there is 10 seconds of mouse movement and then out of focus. It also contains data when a window comes into focus and 5 clicks of the button takes place and the out of focus. This is captured both for an XView window and a Java Window.

###@###.### 2004-12-17 20:23:07 GMT