Hi Gerrit,
Gerrit Voß wrote:
>
> hmm, I would not expect problems with the aspect store as they are
> only written on two occasions, during the initial creation and
> during sync. There should be no interference during both times
> as nobody can access it during the initial creation and while
> syncing everything must be stopped and waiting for the sync
> to happen anyway. Meddling with containers while they
> are synchronized is not safe.
That raises an interesting question though: What about involuntary meddling via
dependent data invalidation or other things that happen in changed()? E.g.
thread A changes a Geometry down the tree, while thread B is syncing a higher
up
node.
Looks like we need to have a slightly stronger rule for different threads on
one
aspect: they have to work on disconnected trees. Allen's code does that
already,
so it's probably not their problem, but in general that might be an issue.
Dirk
------------------------------------------------------------------------------
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
