I just want to make a request relating to jess 5. Is it possible that the
deprication warnings can be removed from the system. I know this is not
that criticat however as java is moving to 1.2 these warnings will
soon become errors.
Thanks
Eamon
-----------------------------------------------------------------
Eamon Gaffney [EMAIL PROTECTED]
Prompter project
Computer Applications Telephone - 087 2203130
Dublin City University Work - 01 7048003
Dublin 9, Ireland. -01 7045618
Surfers Against Sewage.
-----Original Message-----
From: Ernest Friedman-Hill [SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, November 10, 1998 8:06 PM
To: [EMAIL PROTECTED]
Subject: Re: JESS: Serialization of Jess state ..
Well, I have a 'Jess 5.0 alpha' here which I'd like to release soon
- DEEP alpha, still several important known problems. This version does make
all of the core classes Serializable in the Java sense, and there's a
"dump" command which lets you erialize everything out. THe probloem is
that Java serialization is a -pig-. Even a small rulebase results in a
huge .ser file - many megabytes, many seonds or minutes to write or
read. I'm going to have to write special writeObject methods (or
externalization methods) for many classes to make this practical, so
it probably will be a month or three before there's a usable
bload/bsave.
5.0a1 has some interesting new features beside Serialization: most of
all, inheritance of templates and defclasses, and backwards
chaining. Another neat new feature is that Jess will use Bean-like
Events to notify you of various occurrences: the ReteDIsplay class wil
disappear, replaced by a set of Listener interfaces. These Listeners
will be much more fine-grained and will be sufficient to, for example,
build a debugger or graphical interface on top of.
During the 5.0 cycle, I'd like to see other stuff finally
taken care of: the (or) CE, or constraints (|), etc. I also expect a
real whopper of a speed increase as we'll finally start to get direct
translation of rule LHS into Java code.
Warning, though, ahead of time: there are going to be lots of trivial
and not-so-trivial Java source incompatibilities. Many of the public
methods have been renamed or recast according to Java Bean
conventions: name() is now getName(), for example. And of course, as I
said, ReteDisplay is no more.
I think alan littleford wrote:
>
> Ernest,
> just curious as to when (or is it if) the ability to
> serialize/restore Jess state will make it into a released version? I
> know some time ago you were talking about this as a feature to appear
> RSN <g>.
> I have been working on something that might see the light as a
> commercial product, and it would be nice not to have to deliver the
> knowledge base in plain text.
>
> Of course I could always add some user functions to dump state/rules etc
> as encrypted ASCII and read the same, but it would be really nice if I
> could just serialize the whole thing out and in (I think that this would
> offer sufficient security from lightly prying eyes).
>
> As usual, many many thanks for a fine product and finest support.
>
> --
> Alan Littleford
>
>
>
> ---------------------------------------------------------------------
> 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]
> ---------------------------------------------------------------------
>
>
---------------------------------------------------------
Ernest Friedman-Hill
Distributed Systems Research Phone: (925) 294-2154
Sandia National Labs FAX: (925) 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]
---------------------------------------------------------------------
application/ms-tnef
