I think Mariusz Nowostawski wrote:
>
> If we vote, my opinion is: Do things right. If somebody has no time to
> refactor his own Java code, she/he will use older version of Jess - in the
> long run it is always much easier to work with things done right, even if
> it requires refactoring our own code. If there is implemented already
> system dependent on old API, it is dependent on old Jess anyway, so the
> change will have no harm. For ongoing projects, and projects dependent on
> new Jess features, refactoring the code of both, Jess and the project will
> be onlu 'good thing'.
>
> The static code will not have problems running multiple Rete objects on
> single virtual machine? Somehow I am always very suspicious about any
> static code ;o)
Not at all. Static -data- is a problem, but static -methods- are
actualy better, in a way. Since each Rete object won't own a
ReteCompiler object, they will each require a hair less
memory. ReteCompiler is a stateless class - no data at all.
>
> best regards
> Mariusz
>
>
---------------------------------------------------------
Ernest Friedman-Hill
Distributed Systems Research Phone: (925) 294-2154
Sandia National Labs FAX: (925) 294-2234
Org. 8920, MS 9012 [EMAIL PROTECTED]
PO Box 969 http://herzberg.ca.sandia.gov
Livermore, CA 94550
---------------------------------------------------------------------
To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the
list (use your own address!) List problems? Notify [EMAIL PROTECTED]
---------------------------------------------------------------------
