|
From: | Jan Djärv |
Subject: | Re: [PATCH] Re: redisplay-dont-pause is not mentioned in the Emacs manual |
Date: | Tue, 13 Jun 2006 08:36:45 +0200 |
User-agent: | Thunderbird 1.5.0.2 (X11/20060501) |
Kim F. Storm skrev:
Richard Stallman <address@hidden> writes:
Pre-emption probably doesn't work very well with added latency of an internet connection, especially given all the buffering. (The Supdup protocol, which I worked on in 1980 or so, limited the amount of buffering so that pre-emption of Emacs redisplay would work better.) Usually the whole screenful will get buffered anyway.Does the X protocol buffer requests like that? Last time I looked, it didn't do much buffering before transmitting on the wire. But IIRC, there may be some X-aware protocol which does buffering.
For the client (Emacs) X buffers all outgoing requests, until you do an XFlush, XSync or tries to read another XEvent (XNextEvent and such) or until the output buffer becomes full.
For the server, X buffers answers before sending. If there is an answer to be sent but there is another incoming request from a client, the answers are not sent until the input buffer is empty (except for "important" stuff, such as errors).
That said, your changes seem to have a positive effect on slow connections, it feels faster.
Jan D.
[Prev in Thread] | Current Thread | [Next in Thread] |