Finishing the network protocol

Enrico Weigelt weigelt at
Thu Apr 21 12:36:02 PDT 2011

* Andreas Hartmetz <ahartmetz at> schrieb:

> - Have three ID ranges:
>    a) for global objects
>    b) for client-specific objects created by the server (do they exist?)
>    c) for client-specific objects created by the client
d) reserved for future use.

Makes to extra bits.

BTW: should there be any (client visible) global objects at all ?

> - A scheme to recycle object IDs. When a new ID is needed, pick a free
>   one at random. This introduces a problem:
>   Suppose the client destroys object A with ID n, then by chance
>   immediately reuses ID n for object B. 

Simple: let the other side first acknowledge the destruction before
reusing an OID.

> - Specify how parent-child relationships work, e.g. (bad example, the
>   answer is probably no here) is a surface automatically destroyed when
>   its screen goes away? By whom?

What exactly should "goes away" mean here ?
Something like switching GPUs (eg. for power saving) ?

 Enrico Weigelt, metux IT service --

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

More information about the wayland-devel mailing list