Le vendredi 17 novembre 2006 à 20:24 +0100, Lourens Veen a écrit : > On Friday 17 November 2006 13:05, Hamie wrote: > > On Friday 17 November 2006 00:12, Nick LaForge wrote: > > > So, it is called a server, but it only serves itself? Or does it > > > serve video to the screen? I remember X uses weird 'server' > > > terminology. But I understand now what you mean. > > > > There's actually nothing weird about the way it uses server > > terminology. A server provides a service. You have an XServer because > > it provides an X Service to the X clients (Applications) that use it. > > Just like an NFS server provides an NFS service to an NFS client... > > > > You just have to realise that it's named for what it does... > > Well, to be more accurate, you have to understand that the X model sees > rendering of things on a screen and reading events from input devices > as a service. snip I wonder if it's a good idea that the configuration of the X server must have an input devices section. The latter could be handled by another program to which the X server refers in first. If this program fails the X server then refers to its input devices section. it seems to be ridiculous but, keyboard and mouse are critical user interfaces. It's like a car without windscreen wipers in a rainning day. > _______________________________________________ > Open-graphics mailing list > [email protected] > http://lists.duskglow.com/mailman/listinfo/open-graphics > List service provided by Duskglow Consulting, LLC (www.duskglow.com)
_______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
