Linked by Thom Holwerda on Sun 23rd Dec 2007 21:11 UTC, submitted by Kaj de Vos
Syllable, AtheOS The Syllable project has published the source code for Syllable Server. The code to build Syllable is maintained in Builder, the build system. There is a main repository of build specifications and overlays for Syllable Desktop and Syllable Server. The code for Server is now completely published in the source repository. A package of Builder (11 MB) for Syllable Server has been released that corresponds to Syllable Server 0.2 with a few fixes. The procedure to build Syllable Server will be the subject of an article in a future Syllable Newsletter.
Permalink for comment 293288
To read all comments associated with this story, please click here.
RE[4]: syllable desktop
by renox on Wed 26th Dec 2007 22:22 UTC in reply to "RE[3]: syllable desktop"
renox
Member since:
2005-07-06

I think that the locking/ordering of events in the multiple queue design you're suggesting must be quite hard:
Say Window A is selected at the beginning.
a-A mouse event select Window B.
b-A key is pressed.
Depending whether a or b occurred first, the key pressed event must be sent to Window A or B.
So these queue must sometime be synchronised carefuly..

I wonder how BeOS worked, with one queue or with multiple queues?

While I don't know if a different thread&queue to handle each device is interesting, I think that a different thread in the GUI server for each client application makes sense as this simplify the multiplexing of clients: currently an application even if low priority may flood the X server, making the higher priority application appear less responsive than it ought to..
With a different thread in the X server for each client app, maybe the OS scheduling could solve this issue, of course there is still the risk of a priority inversion caused by shared resource (and as the videocard itself is shared, it's not truly possible to avoid sharing)..

Reply Parent Score: 2