Providing shared buffer for applications within Smack environment

[José Bollo]

On Tue, 12 Dec 2017 11:00:08 +0000
Daniel Stone <daniel at fooishbar.org> wrote:

> Hi Pekka,
> 
> On 12 December 2017 at 10:44, Pekka Paalanen <ppaalanen at gmail.com>
> wrote:
> > On Tue, 12 Dec 2017 11:00:23 +0100
> > José Bollo <jose.bollo at iot.bzh> wrote:  
> >> While working for AGL [1], I want to allow applications to receive
> >> the buffers allocated by WESTON. The use of the surfaces/buffers
> >> allocated by Weston is difficult when Smack is activated.  
> >
> > why do you need to make Weston allocate buffers? Why should those
> > buffers be accounted to Weston rather than a client that needs them?
> >
> > E.g. Weston's screenshooting currently has the client allocate
> > buffers, pass them to Weston, and Weston writes into them, then
> > sends an event to say they are done.  
> 
> I assume this is related to the never-upstreamed ivi_share protocol
> extension.
>
> Cheers,
> Daniel

Hi Daniel,

Yes the probability is near 100%

So it could be a design feature issue.

I'm not very aware of this part of the system. Can some one explain me
that share protocol, why it is needed and why it never-upstreamed?

Best regards
Jose