From: "Jan Djärv" <jan.h.d@swipnet.se>
To: grischka <grishka@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: GTK frame changes
Date: Thu, 02 Jul 2009 21:44:14 +0200 [thread overview]
Message-ID: <4A4D0E0E.70405@swipnet.se> (raw)
In-Reply-To: <4A4CF264.6040306@gmx.de>
grischka skrev:
> Jan Djärv wrote:
>> XSync sends a request to the server and waits for a reply. The resize
>> request is sent before that, so the resize should be handeled before
>> the XSync reply is sent.
>
> Yes, but this reply is something in the sense of the X protocol, not
> in the sense of ConfigureNotify. It just means that the X server got
> the resize message when XSync returns. It doesn't mean at all that
> a ConfigureNotify is already in the client queue let alone that emacs
> now knows how big it is.
>
The XProtocol specification (the oldest I have is R6.8, the newest is 7.4,
they say the same thing) says this:
"Whether or not a server is implemented with internal concurrency,
the overall effect must be as if individual requests are executed to
completion in some serial order,
and requests from a given connection must be executed in delivery order
(that is, the total execution order is a shuffle of the individual streams).
The execution of a request includes validating all arguments,
collecting all data for any reply,
and generating and queueing all required events.
However, it does not include the actual transmission of the reply and the events.
In addition, the effect of any other cause that can generate multiple events
(for example, activation of a grab or pointer motion) must effectively
generate and queue all required events indivisibly with respect to all other
causes and requests.
For a request from a given client,
any events destined for that client that are caused by executing the request
must be sent to the client before any reply or error is sent."
I interpret this as for a given X connection, all requests are run to
completion and replies and events are queued in order. Since XSync waits for
the reply, it also means that after XSync has returned, events and replies
generated by previous requests have indeed arrived.
Jan D.
next prev parent reply other threads:[~2009-07-02 19:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 12:53 GTK frame changes grischka
2009-07-02 14:27 ` Jan Djärv
2009-07-02 15:50 ` grischka
2009-07-02 16:18 ` Jan Djärv
2009-07-02 17:46 ` grischka
2009-07-02 19:44 ` Jan Djärv [this message]
2009-07-03 10:53 ` grischka
2009-07-03 11:37 ` Jan Djärv
2009-07-03 12:14 ` Stephen J. Turnbull
2009-07-03 12:43 ` Jan Djärv
2009-07-03 12:47 ` Stephen J. Turnbull
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A4D0E0E.70405@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=emacs-devel@gnu.org \
--cc=grishka@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.