From: <fra...@us...> - 2009-02-17 03:50:47
|
Revision: 1196 http://javapathfinder.svn.sourceforge.net/javapathfinder/?rev=1196&view=rev Author: frankrimlinger Date: 2009-02-17 03:50:43 +0000 (Tue, 17 Feb 2009) Log Message: ----------- WorkerID fix in progress. The concept of ID's was originally necessary because in the task based world, data abstraction was essential for efficiency. Now with shared memory between threads, you might think ID's could be discarded. But they are as essential as ever. The point is that access to underlying data must be serial, that is, it must be via commands posted to the queues and executed serially. Otherwise there will be corruption. On the other hand, the gui world must always be live, so it can't have access to underlying data. Fortunately, the gui world historically only used ID's since it was in an entirely separate task. It is critical that the gui stick with this policy, but there is now no way to enforce it. It is strictly programming on the "honor system." Oh well, the benefits of shared memory still vastly outweigh the risk. Modified Paths: -------------- branches/mango/extensions/mango/Mango/src/mango/core/msg/WorkerCommand.java branches/mango/extensions/mango/ThreadSupport/src/model/Commander.java branches/mango/extensions/mango/ThreadSupport/src/model/SystemBuilder.java Added Paths: ----------- branches/mango/extensions/mango/local/franklocal/rules/rulebase1.zip branches/mango/extensions/mango/local/franklocal/sessions/<Untitled> branches/mango/extensions/mango/local/franklocal/sessions/b.zip branches/mango/extensions/mango/local/franklocal/sessions/bother.xml branches/mango/extensions/mango/local/franklocal/sessions/bother.zip branches/mango/extensions/mango/local/franklocal/sessions/test.xml This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |