On Mon, Feb 8, 2016 at 2:02 AM, Pekka Paalanen <[email protected]> wrote:
> On Fri, 5 Feb 2016 21:03:20 +0100 > Benoit Gschwind <[email protected]> wrote: > > > Hello, > > > > I will add my opinion as called for opinions. First I made a quick > > brainstorm following previous proposals about solutions available. I see > > 3 mains choice: > > Hi, > > thanks for looking into this. > > > 1. a structure that user fill and pass to the back end; > > 2. an opaque structure that the user fill through helper function; > > 3. a free list of key/value pair. > The Wayland message api only allows sending of a small set of primitive data types. So if you have a "structure" that is more complex than one of those data types, the only way to send it is through multiple arguments to (possibly multiple) Wayland requests. Therefore it seems like it is limited to solutions 2 and 3, right? A list of key/value pairs has a huge advantage that intermediate layers do not need to know anything about the data.
_______________________________________________ wayland-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/wayland-devel
