Changes between Version 26 and Version 27 of Java API

Timestamp:

12/17/12 13:21:57 (12 years ago)

Author:

jorisborgdorff

Comment:

--

Java API

@@ -362 +362 @@
    entrance = addAsynchronousEntrance("entranceName", double[].class);
 }}}
-Whenever a message is sent through this type of entrance the sending submodel does not have to wait until the receiving MUSCLE instance has received the data. This mode of operation slightly increases the latency and involves keeping alive an additional thread. There can be a performance gain if the submodel that sends the data, afterwards immediately continues its computations and does not have to wait for input from another submodel. It may also speed up sending multiple messages shortly after each other. The gain will only be noticable if data is sent across multiple MUSCLE instances.
+Whenever a message is sent through this type of entrance the sending submodel does not have to wait until the receiving MUSCLE instance has received the data. This mode of operation slightly increases the latency and involves keeping alive an additional thread. There can be a performance gain if the submodel that sends the data immediately afterwards continues its computations and does not have to wait for input from another submodel. It may also speed up sending multiple messages shortly after each other. The gain will only be noticable if data is sent across multiple MUSCLE instances.
 
 Using the addAsynchronousEntrance call is equivalent to adding the conduit filter "thread" to the beginning of the conduit entrance filter stack, as explained in the [[Configuration|configuration section]].