Thank you for your input! A separate KB for each user seems to me to be a "cleaner" solution at this time since I'm not sure how to work with rule packages and parametrized facts between users. I was also considering using the session for testing purposes, letting the user create test cases for his configuration.
Regarding the expense of creating the KB I have seen some suggestions of only creating it the first time the user loggs in and then serializing it and then loading it from the database when the user re-connects. I am most worried about the heap/perm gen requirements for the jvm when having 100 KBs at the same time, each running with multiple sessions. I am definitely going to evaluate the rules and see if they can be made to be more generic and allow the application to use only sessions. Thanks again for the quick responses! -- View this message in context: http://drools.46999.n3.nabble.com/Drools-scalability-in-home-automation-scenarios-tp4020855p4020868.html Sent from the Drools: User forum mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-users
