On Jun 30, 2014, at 6:20 PM, Robert O'Callahan <rob...@ocallahan.org> wrote:
> On Tue, Jul 1, 2014 at 11:46 AM, Patrick Walton <pcwal...@mozilla.com> > wrote: > >> On 6/30/14 4:44 PM, Robert O'Callahan wrote: >> >>> BTW have you or anyone else working on Servo looked at >>> TextureClient/TextureHost in Gecko? Getting buffer management interfaces >>> correct across many platforms with multi-process and robustness in the >>> face >>> of crashes and platform quirks has proven to be very hard. I think we're >>> in >>> a good place now but we went down many blind alleys so there's some >>> valuable lessons to be learned. >>> >> >> By TextureClient/TextureHost I assume you mean cross-process texture >> sharing? If so, yes, we have been doing this from day one. (We have to, >> because we do painting on a separate thread.) >> > > Yes. But if you haven't got robust support for D3D10 and Android gralloc > and Windows Media Foundation accelerated video decoding and all that sort > of thing, you probably don't have the design right unless you're cleverer > and luckier than the rest of us :-). How much of that changed the basic nature of the abstraction and how much of it was just difficult platform-specific implementation work? Most of my experience is with IOSurface on Darwin, which is comparatively sane. Cameron _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
