I am OK with that as long as examples and doco show the newStatelessSession generously. <br><br>I never liked the weakhashmap - it kind of got rid of the leak on paper, but put a load on the GC at the worst possible time.<br>
<br>Stateless and Statefull are great ideas I think. WorkingMemory is then either just an interface, or mainly a &quot;concept&quot; that people talk about. Everything else out there likes to use the word session (eg hibernate) so the semantics of it are pretty well understood.
<br><br><div><span class="gmail_quote">On 4/23/07, <b class="gmail_sendername">Mark Proctor</b> &lt;<a href="mailto:mproctor@codehaus.org">mproctor@codehaus.org</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
currently working memories are auto garbage collected once you null<br>them, by using a weak hashmap in the RuleBase. I&#39;m currently adding<br>async methods to the working memory, which means that the weak hashmap<br>no longer works. So I&#39;m thinking of using a normal hashmap, which means
<br>people MUST call workingMemory.dispose() or they will get memory leaks,<br>are people ok with that? I now have ruleBase.newStatelessSession which<br>won&#39;t adding the session to the Map, to avoid having to call dispose()
<br>for stateless sessions.<br><br>Mark<br>_______________________________________________<br>rules-dev mailing list<br><a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/rules-dev">
https://lists.jboss.org/mailman/listinfo/rules-dev</a><br></blockquote></div><br>