[pkg-x2go-devel] Bug#766299: nxproxy: BIG-REQUESTS patch builds but fails at runtime

[paul.szabo at sydney.edu.au]

Dear Mike,

While looking into the handling of sequence numbers, I notice:
 
  http://www.x.org/releases/X11R7.7/doc/xproto/x11protocol.html
    ... Every request on a given connection is implicitly assigned
    a sequence number, starting with one ...
 
Does that mean that each connection should keep its own state of
sequence number (and caches etc)? Whereas, nxproxy (both -C and -S
instances) seems to keep just one state, across all clients and
connections.

Though admittedly, even when nautilus is the first and only client, it
still fails and maybe complains (as reported already); in my testing it
may get to show its window, then fail as the mouse pointer moves within.

Thanks, Paul

Paul Szabo   psz at maths.usyd.edu.au   http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics   University of Sydney    Australia