Changes between Version 21 and Version 22 of Java API

Timestamp:

12/03/12 16:22:36 (12 years ago)

Author:

jorisborgdorff

Comment:

--

Java API

@@ -357 +357 @@
 When using a shared data entrance, MUSCLE will try to not copy the data that is sent through the conduit. This means that any change that is done by a conduit filter or another submodel that receives the data, also affects the original data. In most cases this is not desirable, since it violates the separation that different submodels have. Moreover, it is fragile since it only works if the sending and receiving submodel are in the same instance, and there is no filter applied that copies the data in some way.
 
-The shared data conduit entrance does make sense when the sending submodel will not use the sent data in any way, since then another submodels may modify it as it pleases.
+The shared data conduit entrance is useful when the sending submodel will not use the sent data in any way, since then another submodel may modify it as it pleases.
 
 The second alternative conduit entrance is the asynchronous conduit entrance, which is created as