3 ms·
Maybe this one [1] from 1987? It says: > There are many race conditions that must be dealt with in input and window management because of the asynchronous natu
by ptx 10mo ago
Maybe this one [1] from 1987? It says:
> There are many race conditions that must be dealt with in input and window management because of the asynchronous nature of event handling. [...] However, not all race conditions have acceptable solutions within the current X design. For a general solution it must be possible for the manager to synchronize operations explicitly with event processing in the server. For example, a manager might specify that, at the press of a button, event processing in the server should cease until an explicit acknowledgment is received from the manager.
[1] https://web.mit.edu/6.033/2006/wwwdocs/papers/protected/xwindows.pdf https://web.mit.edu/6.033/2006/wwwdocs/papers/protected/xwin...
- mananaysiempre 10mo agoI went and checked, and it was an SPE article from 1990[1]: “Why X is not our ideal window system” by Gajewska, Manasse, and McCormack. Section 3 has extensive diagrams of various races, including ones between clients and the window manager. Was even discussed here at one point[2], it turns out. Where I came across it I’m not sure (on X.org[3] possibly?). [1] https://dx.doi.org/10.1002/spe.4380201409 https://dx.doi.org/10.1002/spe.4380201409, https://people.freedesktop.org/~ajax/WhyX.pdf https://people.freedesktop.org/~ajax/WhyX.pdf or http://os.4uj.org/WhyX.pdf http://os.4uj.org/WhyX.pdf [2] https://news.ycombinator.com/item?id=15120308 https://news.ycombinator.com/item?id=15120308 [3] https://x.org/wiki/XorgDeveloperDocumentation/ https://x.org/wiki/XorgDeveloperDocumentation/