Hi everyone, I'm currently integrating JESS into my web application and the architecture is typical; running rete.runUntilHalt() and asserting a shadow fact for an incoming HTTP request. But as more and more rules are developed, I'm thinking to partition the rules into modules.
Now, suppose I have 2 module, moduleA and moduleB, and some rules are defined to match the same set of shadow facts on the LHS. In essence, I could "switch" the execution logic by either focusing moduleA or moduleB, and the decision for which module gaining control is depends on the screen the user is in. However, there is an incoming the fact which should be running in moduleB but there might be chances that rule engine is processing another requests and moduleA is the current focus; if the incoming fact is assert at that time, it might be running moduleA instead of moduleB. So, might I confirm if the above scenario would happen? Is there any workarounds to avoid the unnatural execution? What would be the orthodox way to implement the module control flow then? Any help or opinion would be appreciated. Thank you very much, everybody!! Best Regards, folderman -- View this message in context: http://www.nabble.com/Module-and-Concurrency-tf4022222.html#a11424331 Sent from the Jess mailing list archive 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] --------------------------------------------------------------------
