Re: Re:FW: XFree86 future

Mark Vojkovich writes:
 > 
 >    I've not see the protocol be a significant issue for most 2D
 > rendering.  It is for PutImage, but that's why the shared memory
 > extension was created and that fixed the problem.  
 > 
 > 
There is the round trip issue. There are situations where a client
and the server need to synchronize frequently so that requests cannot
be accumulated and handled asynchronously. To some extend it is
an Xlib design problem. It cannot be fixed entirely within the Xlib
API, an Xlib replacement is needed. Some issues were already resolved
by introducing client side font rendering.
1. Frequent round trips are undesirable as they require frequent context 
   switches. 
2. X applications on fast but high latency networks (like DSL) become
   painfully slow due to round trips.

Egbert.