I am thinking about using Jess to implement a business logic servlet.
It would be great to be able to specify business logic declaratively in
jess rather than procedurally in java/perl/python. I want to create a
four tier website that looks like:
browser <-> presentation layer <-> business logic <-> storage
(xslt servlet) (jess servlet) (sql dbms)
All form posts would go to the business logic servlet.
On initialization the jess servlet would load a clp file specified in a
properties file into a shared rete engine.
The .clp file will contain some rules that have HttpServletRequest
information in the condition and some rules that write a response to an
HttpServletResponse.
I am trying to figure out how to pass http requests into Jess so they are
most efficiently processed by rules. My instinct is to create a template
like:
(deftemplate request "http request object"
(slot response) ;HttpServletResponse for writing the response
(slot headers) ;java.util.Hashtable
(slot cookies) ;java.util.Hashtable
(slot parameters) ;java.util.Hashtable
)
My questions are:
1. can the same rete engine process requests from multiple threads
simultaneously or should I create a Rete engine pool?
2. what is the best way to pass an HttpServletRequest into Jess?
3. how do I clean up after processing a request (so I don't accumulate a
large number of obsolete request facts)?
4. is this a good idea at all?
-Alex-
___________________________________________________________________
S. Alexander Jacobson i2x Media
212-697-0184 voice 1-212-697-1427 fax
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
