https://wiki.eclipse.org/index.php?title=Talk:SMILA/Documentation/QueueWorker/ExperimentalFeatures&feed=atom&action=historyTalk:SMILA/Documentation/QueueWorker/ExperimentalFeatures - Revision history2024-03-28T13:06:41ZRevision history for this page on the wikiMediaWiki 1.26.4https://wiki.eclipse.org/index.php?title=Talk:SMILA/Documentation/QueueWorker/ExperimentalFeatures&diff=161733&oldid=prevTmenzel.brox.de: New page: hi ivan, reading this page i dont quite get it. i guess i would have to look into the code to understand it... plz add more information on the ramifications either by link or in place. ...2009-07-02T13:08:36Z<p>New page: hi ivan, reading this page i dont quite get it. i guess i would have to look into the code to understand it... plz add more information on the ramifications either by link or in place. ...</p>
<p><b>New page</b></p><div>hi ivan,<br />
<br />
reading this page i dont quite get it. i guess i would have to look into the code to understand it...<br />
<br />
plz add more information on the ramifications either by link or in place.<br />
<br />
i assume it works like the following:<br />
# by default the router will persist the record in the blackboard and do the filtering such that not all content is carried on the Q<br />
# this can be turned off by BlackboardSync="false"<br />
# not described:<br />
## the name BlackboardSync suggests that this is a setting that is remembered for all records routed by this rule and processing steps down the road wont even attempt to to put it into the BB. <br>is that so? <br>if not: what happens when this is done all on the same host and a listener will get the record? an exception due to mussing info in the BB?<br />
## when router is BlackboardSync="true" and listner InitiallySet="true":<br> what happens?</div>Tmenzel.brox.de