The "loop and a half"

Marko Rauhamaa marko at pacujo.net
Mon Oct 9 11:56:08 EDT 2017


Grant Edwards <grant.b.edwards at gmail.com>:

> On 2017-10-09, Marko Rauhamaa <marko at pacujo.net> wrote:
>> The problem is it's too low-level ("mechanism, not a policy"). What
>> we'd need is this setup:
>>
>>    +---------+
>>    | client  |
>>    +---------+
>>    | toolkit |
>>    |   RPC   |
>>    +----+----+
>>         |
>>         | TCP
>>         |
>>    +----+----+
>>    | toolkit |
>>    |  server |
>>    +----+----+
>>         |
>>         | Local
>>         |
>>  +------+------+
>>  |   Wayland   |
>>  |  compositor |
>>  +-------------+
>
> But then you need to re-impliment that for each and every toolkit.
> With the old X11 scheme, it only need to be implimented once.

The solution is that the toolkit RPC sends (or is prepared to send) the
toolkit server plugin to the generic remote server. In fact, that's how
web pages are implemented using JavaScript (with the roles of the server
and the client reversed).


Marko



More information about the Python-list mailing list