I would suggest that you read "Expert Systems" by Giarratano/Riley (pub.
PWS-Kent?)
It goes through a number of examples of both inefficient and well written
rules. More importantly it shows how to design your facts *and* rules to
model your state/problem spaces efficiently.
Good luck!
alanm
> -----Original Message-----
> From: Venkat [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, September 23, 1998 8:36 AM
> To: [EMAIL PROTECTED]
> Subject: JESS: Jess/Rete
>
> Hi,
>
> I am using Jess for writing filtering rules for an
> email software.
>
> Assume there are 10,000 users and
> each user has his own rule set for message forwarding
> and priority setting.
>
> For eg:
> If email is recvd on Monday and the user
> is Mark then forward it to Marks's work email address and set the subject
> as high priority.
> In Jess parlance, each user has more than one rule defined.
>
> I would like to know - to make "best use" of Rete efficiency
> do we need to assert every rule for each user
> in the fact list, so that when a new message comes in
> the fact is already asserted and it will go through right away -
> this will mean a huge working memory. Or do we strike a balance ?
>
> Well, I am trying to make use of Jess (Rete) in the best possible way
> for the above application primarily in terms of "speed" - any suggestions
> ?
>
> Thanks,
> Venkat
> ---------------------------------------------------------------------
> 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]
> ---------------------------------------------------------------------
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
