I would like to request that some Jess expert please post some best practices
for pooling of Jess objects.  I am specifically interested in creating a
pool of Rete engine objects for use in a J2EE application.  The application
needs to scale to several hundred concurrent users and we are using Jess to
process business rules on a multitude of pages.  Throughput is obviously
going to go in the tank with a single engine processing all requests.  It
seems to me that this would be a common problem for Jess developers and it
would make sense to have an area on the Wiki dedicated to the topic.  Please
let me know if there is already some guidance on this topic available.
-- 
View this message in context: 
http://www.nabble.com/Jess-Engine-Pooling-tf2045818.html#a5633021
Sent from the Jess forum at Nabble.com.
--------------------------------------------------------------------
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]
--------------------------------------------------------------------

Reply via email to