Some of my thoughts on input for wayland

[Enrico Weigelt]

* Chase Douglas <chase.douglas at canonical.com> schrieb:

> Can you describe more here? If you are meaning a real computer
> "process", I think it would help to split input and output display into
> separate processes. Practically every system shipping in the future will
> have multiple cores, so making the input system wait around while output
> does its thing seems unnecessary.

Of course, processes are the natural way of parallelism (on mainline
architectures). But we'll have to differenciate between separate
layers of input events. Things like transforming lolevel scancodes
into some highlevel keystrokes (eg. mapping the scancode for 'A' to
some "key A was pressed" event or decoding mouse protocol into
movement events) probably would find a good place in separate
server processes (eg. little 9P servers, and their clients capable
of dynamically reconnecting, so the servers can be plugged easily).
But at the windowing layer - transforming an global mouse click into
an click event _within_ some window - we need the window geometries,
so that should live in a process which knows about all of this.
(this doesn't necessarily doesn't need the actual _display_ server,
but the one who actually handles window positioning/sizing).


cu
-- 
----------------------------------------------------------------------
 Enrico Weigelt, metux IT service -- http://www.metux.de/

 phone:  +49 36207 519931  email: weigelt at metux.de
 mobile: +49 151 27565287  icq:   210169427         skype: nekrad666
----------------------------------------------------------------------
 Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------