>> These are all tricky and hard questions. I'd like to address this >> general issue in Charlemagne (the next major Jess release) but I >> currently don't have a design for how this would work. It's much >> harder than you might think. Ideas are welcome (not just "Jess should >> perform such-and-such magic" kind of ideas, but implementation ideas, >> especially.)
>Good to know, though I'm afraid I can't be of much help, yet. Sounds for me like a classic design of an observer pattern. For this of course you have to implement your own collection class. But is not so hard as you think, because it is only in this case a wrapper. So I think we must first define what would happen if a collection is changing using add() or remove(). My understanding is that in this case Only facts are going to be adding or removed. Or have the rules also automatically be fired in this case? If yes, then you need the possibility to create central observer objects where you can register the rules for firing. After that the observer is going to be registered in the objects which are notifying him if some events are occurring. (or the other way round) So the wrappers have a link to the observer and the observer has links to the specific rules. Am I completely wrong with this concept? If not then we could go forward and discuss some specific issues. Regards Mark -------------------------------------------------------------------- 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] --------------------------------------------------------------------
