<p dir="ltr">The facts should be immutable, so you should remove them and insert again when they change.<br>
If your facts change often, you have to consider to use fusion where your facts will be events.</p>
<div class="gmail_quote">On 14 Feb 2013 04:29, "mohdejaz74" <<a href="mailto:mohdejaz74@gmail.com">mohdejaz74@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello,<br>
<br>
I'm working on a project which uses Drools as a component. It is connected<br>
to a web server. Every time a request arrives to web server, it in turn<br>
loads the facts and invokes fireAllRules. Facts do change over time but<br>
rules do not ... I'm bit concerned that this may not be correct of using<br>
Drools, since we are constantly doing setup /tear down.<br>
<br>
Keep facts in memory and updating them when necessary - that requires major<br>
change in the architecture of the application.<br>
<br>
I want to know - has anyone done something similar? Does it lead major<br>
problems in future? Performance Issues?<br>
<br>
Regards<br>
Ejaz<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href="http://drools.46999.n3.nabble.com/What-is-the-correct-approach-towards-using-Drools-tp4022291.html" target="_blank">http://drools.46999.n3.nabble.com/What-is-the-correct-approach-towards-using-Drools-tp4022291.html</a><br>
Sent from the Drools: User forum mailing list archive at Nabble.com.<br>
_______________________________________________<br>
rules-users mailing list<br>
<a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
</blockquote></div>