Also I believe (from memory) that in Jrules it works the same under the covers (but "from memory" as it is not freely available). Front ends built on top of the rule engines can generally automate change notifications at RuleBase build/compile time (so you get the best of both worlds).
-----Original Message----- From: Mark Proctor [mailto:[EMAIL PROTECTED] Sent: Friday, 4 November 2005 9:23 AM To: user@drools.codehaus.org Subject: Re: [drools-user] Comment on drools performance. Read the comment he made, we do support that via JavaBeans property change listener - but using modifyObject is actually more powerfull as you can "batch" your chages thus removing the number of propergation cycles on the same object. Mark Felipe Piccolini wrote: > Guys, > > In this link a guy comment on Drools's performance and some people in > my company are worried about the impact this can produce on the > application (beacuse of course I introduced Drools on it). I know > this is not a real problem, and we are using rule engine in a smart > way so working memory and rules are no over loaded, but the top > managers need more facts than just my opinion, and Im asking all of > you guys about experiences and real comments about this link and > about your application performance and scalability using Drools. > > > http://bizrules.eclipsedevelopersjournal.com/some_thoughts_about_drool > s.htm > > Thaks a lot. > > > > ---------------------- > Felipe Piccolini > [EMAIL PROTECTED] > > > >
