Hi Folks, Well, I spent a little time today working on making Jess 'Serializable', so you can do things like bload/bsave as in CLIPS, or saving Defrule objects in a database. I've got a first cut working using ordinary Java Serialization; I only had to mark a half-dozen scattered members as transient, have all the classes implement Serializable, and write one 'readObject' method. The advance work for Jess 4.1 took care of most of the problems. Anyhow, the primary motivator for bload/bsave is speed - loading previously-compiled rules (or a fact-populated Rete network) is likely going to be faster than compiling the rules from a file at runtime. I now need to work on optimizing bload/basave for speed and image size. I thought perhaps that one of you might have a rulebase all prepared that has the following characteristics: 1) Large - takes a macroscopic amount of time to read in (at least 10 sec on a 300MHz Pentium II). One hundred rules minimum, preferably more. 2) Compiles on stock Jess 4.1 (no user extensions). 3) Heterogeneity - uses a wide range of different Jess features. If anyone has such a thing they'd like to share with me, I'd be grateful. If you do, send it to me privately at [EMAIL PROTECTED], NOT as a reply to the list (I'm sure most people wouldn't want it clogging their inbox!) Thanks in advance. --------------------------------------------------------- Ernest Friedman-Hill Distributed Systems Research Phone: (510) 294-2154 Sandia National Labs FAX: (510) 294-2234 Org. 8920, MS 9214 [EMAIL PROTECTED] PO Box 969 http://herzberg.ca.sandia.gov Livermore, CA 94550 --------------------------------------------------------------------- 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] ---------------------------------------------------------------------
