ernest, you took my statements in the wrong sense. I
dint't make any complaint on you. You are doing great.
I quoted on ILOG and Blaze Advisor just to make Greg
Ball to understand that putting the rule engine as an
EJB component is sometimes necessary and ILOG & Avisor
have that features.
Chinnaswamy
--- friedman_hill ernest j
<[EMAIL PROTECTED]> wrote:
> I don't have a marketing department, or an
> applications department, so
> I don't have the resources to develop EJB-based
> demonstrations or
> fancy powerpoint presentations. All I can do is tell
> the truth, as I
> see it.
>
> -- A large knowledge-base will lead to large Rete
> objects (many
> megabytes in use.) If an EJB server wants to
> passivate/activate such a
> large object, that process will be very inefficient
> compared to having
> the engine in-memory all the time.
>
> -- Keeping the facts in a database won't make the
> engine smaller; it's
> the sets of partial matches that take up memory, and
> being transient
> data structures, they have to be held in the rule
> engine -- UNLESS you
> explicitly create tables for them and store them on
> a database -- a
> bizarre and possibly very inefficient process; OR,
> you don't keep
> partial matches, in which case the rule engine will
> be very slow (see
> the next item.)
>
> -- Keeping the rules "in files" can only mean one
> thing that I can
> think of: that rules are if-then statements executed
> serially without
> being compiled into anything like a Rete network. If
> this is the case,
> then the memory problems described above go away.
> But if there are
> many facts, serial rule execution is insanely slow
> -- polynomial slow
> -- and that's the whole reason for inventing the
> Rete algorithm in the
> first place. Rete trades space to get speed.
>
> Despite all of this people -have- used Jess
> successfully in EJB
> environments, and in servlet environments, and in
> applet
> environments. I just want you to be aware of the
> issues. I doubt the
> issues with using Jess are any different than those
> you'd face using
> any other rule engine designed for high throughput
> -- but as I said,
> here you're dealing with a developer, not a
> marketing department.
>
>
> I think chinnaswamy gounder wrote:
> > ...
> > Of course, a rule engine can be a stand alone
> product
> > receiving information from enterprise java bean
> > objects and serve them. This I am fully aware.
> >
> > But for your kind information, I need to tell you
> a
> > few things. Recently ILOG made a presentation in
> my
> > office and claimed that in JRules, the rule
> repository
> > is put in Data Base and the rule engine can a
> stateful
> > session bean. Pl. take a look at the URL:
> >
>
http://industry.java.sun.com/javanews/stories/story2/0,1072,22698,00.html.
> > There it is written,
> >
> > " ILOG JRules works on a Java client in the form
> of an
> > applet, or on a server as a servlet, EJB
> component,
> > CORBA component, or COM+ component"
> >
> > In another presentation by Brocat Pte Ltd, their
> Blaze
> > Advisor Rule engine stores the rules in files and
> the
> > rule engine can be a stateful or stateless session
>
> > bean.
> > ...
>
>
>
>
---------------------------------------------------------
> Ernest Friedman-Hill
> Distributed Systems Research Phone: (925)
> 294-2154
> Sandia National Labs FAX: (925)
> 294-2234
> Org. 8920, MS 9012
> [EMAIL PROTECTED]
> PO Box 969
> http://herzberg.ca.sandia.gov
> Livermore, CA 94550
__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/?.refer=text
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
