I think Serge Mankovski wrote:
>I have an implementation of an ICQ-like chat system that uses Jess and exchanges
>messages in KQML form using tuple space. I have my own implementation of a tuple pace
>server that uses Linda
>like primitives for coordination and signaling between software components. (sorry,
>no Viyager) This is a part of our agent testbed that we use for the project. You can
>take look at
>http://micmac.mitel.com. Look under Forum.
>
>Actually I've been thinking about setting up our own chat system for Jess community
>using this tool. I am also interested in expending on it (to have something as
>"evaluate" in emacs so you
>will be able to add custom rules in the clips engine that runs the chat server) How
>is that
This is very interesting. I was not able to connect to the server you mentioned
(but I will keep trying), but from what you wrote I understand you are addressing the
same problem I was looking at - the distributed inference engine. What you have
covers a good deal of that space - multiple inference engines, messaging and database.
Some other aspects are interesting too. For example, if the completion of a rule
evaluation depends on some remote rule evaluation, I think there should be a way of
dealing with success and failure in a larger way than simple True and False; maybe the
time it takes is very long, or a communication line went down, not to mention more
complex cases.
Another thing is transaction processing in the persistent and transient spaces - how
to insure good performance and data integrity when agents are passing data to each
other and storing it at the same time. Sometimes we have to deal with multiple local
persistent storages, some central persistent storages, transient (in memory) storage,
and a lot of funny stuff that is just in transit. This may get a bit confusing.
The common sense is that ObjectSpace implemented a solid and efficient agent
infrastructure and distributed objects, that includes security and transaction
processing (in a future release). So maybe this part can be used and build on top of
it some more sophisticated agent behavior and messaging with Jess and KQML.
Interpreters for KQML and discourse managers for agent conversations can very nicely
implemented in Jess (by the way is this what you do?).
Best regards,
Alex Bejan
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
