At 01:54 PM 2/8/99 -0800, you wrote:
>In Jess, the nodes of the Rete network are instances of the various
>subclasses of jess.Node. The class jess.ReteCompiler has the
>unenviable task of assembling network fragments from rules jess.(Defrule
objects).
>
This brings up a question that I have wanted to investigate. Can I parse a
Jess ruleset and create the jess.(Defrule objects), but postpone the
creation of the Rete network? Basically, break the current parse method
into two steps. I have two reasons for asking this.
1. I'm building a graphical rule editor for Jess (more to come in another
message...), and I would like a quick way to check syntax without incurring
the overhead of creating the Rete. Also, I want access to the various
Defrule, Pattern, Test1, etc. objects resulting from the parser. But, I
don't need the Rete at this point.
2. In a multithreaded server, e.g. a servlet, I would like to parse the
ruleset once, save the jess.(Defrule objects), and then create a new Rete
for each connection thread. But, all Rete networks could be generated from
the same parser results. I haven't tried to benchmark this, but seems like
I could save some overhead by not parsing the rules over and over again. I
currently use a resource pool approach for this. When the server starts, it
creates several Rete objects, then allocates them to users and resets when
done. But, I still have to parse the rules separately for each instance of
the Rete.
Cheers,
Dave Carlson
---------------------------------------------------------------------
To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the
list. List problems? Notify [EMAIL PROTECTED]
---------------------------------------------------------------------
