> I think David Whitten wrote:
> But do they have any business knowing that you choose to have
> an agenda abstraction to make the rete engine work ?
> What happens the next time you refactor and find that some
> other specialized abstraction in the proper situation gives you
> a 15% performance win ? It seems that the cost of a subroutine
> call is preferable to having to maintain high density communication
> with a lot of developers who aren't working on that code anyway.
I tend to agree. In fact, I would argue that the best solution
is to provide different layers of access, so that if a given system
had good reason to think in terms of agendas, etc., it could avail
itself of that layer, while the average Jess application would continue
to think just in terms of engine.run, engine.reset, etc. (engine =
Rete).
Sidney
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
