On Tue, Mar 24, 2009 at 12:05 AM, Gerrit Voß <[email protected]> wrote: > > Hi, > > On Mon, 2009-03-23 at 21:43 -0600, Allen Bierbaum wrote: >> On Mon, Mar 23, 2009 at 8:27 PM, Carsten Neumann >> <[email protected]> wrote: >> > Hello Allen, >> > >> >> >> >> * Change lists: As discussed in another posting, we think that the >> >> change list should be thread safe and that as long as we call >> >> commitChanges() we should be good. >> > > > One other thought, could you call commitChangesAndClear instead of just > commitChanges as you transfer your containers from one thread to > the other. commitChanges leaves some entry linking intact and might > have some side-effects. I have to think through the details but the > AndClear version should be safer.
I think my use of the work "sync" is a bit confusing. There is no sync in terms of commiting a change list across threads in our case because everything is in the same aspect. I was using "sync" to mean the point in our application where we know the background request has completed and we hook it up to the foreground scenegraph. In effect we are handing off control of the fc's from background to foreground because the bg thread won't touch them anymore and the foreground thread now has full control to do with them as it will. -Allen ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
