Hacker News new | past | comments | ask | show | jobs | submit login

I'm confused by your diagram. The "X11 Client" is your app (literally, from a process perspective), and the X server displays it.

Edit: You know what, I should be less passive-aggressive about that. I'm not confused by your diagram, it's just wrong. :-)




Oh, right, on a local machine I guess the X11 server doesn't need a client before the compositor.


Maybe what you really mean is:

Display <- X server <- Compositor/WM <- X server <- Your app

Where compositor/WM and your app are X clients, i.e. there's lots of context switches between clients and the server.

I personally don't see much wrong with this design BTW, despite the context switches X is pretty smooth even on some pretty wimpy hardware (eg. Raspberry pi, or Nokia N900, or the wimpy Pentiums I ran X on 15 years ago).




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: