I think Michael Don Knapik wrote: [Charset iso-8859-1 unsupported, filtering to ASCII...] > > Say you have a Java system that produces event objects (lots of them).
Objects will stay in working memory until you remove them. Generally, what you do is "expire" old objects. Each event fact would need a timestamp slot. You can then have a current-time fact, and a rule that fires and retracts an event fact when the timestamp is some specified interval before the current-time. Alternatively, you can have a query that runs periodically, collecting old events and removing them. If your rules match only single events, then another alternative is to remove each event as soon as any processing is done, perhaps using a low-salience rule for this purpose. --------------------------------------------------------- Ernest Friedman-Hill Science and Engineering PSEs Phone: (925) 294-2154 Sandia National Labs FAX: (925) 294-2234 PO Box 969, MS 9012 [EMAIL PROTECTED] Livermore, CA 94550 http://herzberg.ca.sandia.gov -------------------------------------------------------------------- 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] --------------------------------------------------------------------
