<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2658.24"> <TITLE>Re: What about glxCopyContext</TITLE> </HEAD> <BODY> On Tue, 2005-05-17 at 12:17 -0400, Matthias Hopf wrote: > > >We need a mechanism for sharing texture data between different > > >*processes*. As the implications and exact requirements for that > are not > > >completely clear so far, we decided to delay this until Xgl matured > a > > >bit. Then we'll come up with a proposal for another extension. > >  > > I guess I'm not fully aware of the issues yet.  In terms of  > > *processes* there's: > >  > > 1. The EGL layer/driver + XGL server + compositor > > 2. The OpenGL/Xlib application(s) > >  > > Right?  Or is the compositor in a different process? > > Yes it is. It typically would be the window manager, though it can be > a > different process (and actually usually is at the moment, because > AFAIK > no window manager with embedded compositing has been released yet). xfwm 4.2 and kwin 3.4 have compositing managers built in optionally. Last I heard there were plans to integrate Luminocity into Metacity as well. -- Michel Danzer, Linux Software Engineering       \   Tel: +1 905-882-2600 ATI Technologies Inc., Markham, Ontario, Canada  \       Extension: 3550 </BODY> </HTML>