Why Isn't X11 Thread-Safe?

blackcoot asks: "I've just spent a couple very frustrating days trying to figure out what 'unexpected async reply' means and fixing it. The problem is a result of the fact that X11 simply isn't designed to handle events from more than one thread at a time. Why? Given that more and more often, people are writing multi-threaded GUI applications, are there fundamental design decisions in X11 that make dealing with receiving events from multiple threads simultaneously, impossible? Or was the protocol never designed to handle concurrent updates? More to the point, is there an easy way in Qt (short of deriving a new widget for every widget and overriding it's paintEvent to lock the library first, paint, then unlock as Trolltech's docs seem to suggest) to make this problem go away?" I'm not sure if things have been done in recent revisions of XFree to fix this problem, but this message, from February of last year, might help some of you out that are suffering from this problem. Any ideas if this problem has been fixed in recent versions of XFree?

OFFICIAL FIRST POST DECLARATION NOTICE

[Anonymous Coward]

Hello,

Pursuant to the universal Slashdot Act of First Postage, it is hereby posted that this post, article number referenced above, is a declaration for first post in the following circumstances:

1. This post claims first post in this article, persuant to the limitations outlined in 3(a).
2. This post declares under Slashdot Bylaw TROLL 13.22 that this first post shall be unique, and all other posts of similar nature shall be moderated as accorded by Slashdot Bylaw TROLL 13.22b
3a. According to the Slashdot Bylaws, this post recognizes that other posts have been made to this article.
3b. According to the Slashdot Bylaws, the current reader agrees to accept this post as the rightful first post.

Re:X sux and is the biggest thing holding back lin

[Gordonjcp]

Hmmm, a framebuffer with network access crufted in on top? It'll never fly...