I apologize if the question has been asked and answered - I am new to Jess and rules engines. I must say that the Jess In Action book was very helpful and I was in fact able to get a set of rules up and running for a Dependency Management module (things depend on resources which depend on other resources etc). Anyhow, here is my question///
We plan to use Jess in a multi-threaded, j2ee environment; one of the applications is similar to the catalog example in the book. The characteristics in general are: - large # of 'base' facts - of the order of 100,000 to 200,000 (similar to catalog entries) - the base facts change slowly - moderate load of about 1-5 requests per second - the rules engine is invoked for a new fact which is asserted, conclusion reached and then retracted Given that, should we have RETE multiple engines that are instantiated? Perhaps a pool of 10 that we can use on demand? How about data sharing? When the base facts are updated, the updates need to be applied to all the RETE engines. -------------------------------------------------------------------- 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] --------------------------------------------------------------------
