Hi,
We've been developing an agent platform in Broadcom for a couple of years now,
and have always used CORBA as the distribution mechanism; CORBA has some nice
features like language and OS independence, which we thought would be valuable.
To date, we have a number of language bindings for agents developed for our
platform, "Agent Services Layer" (ASL).
The languages include JESS, CLIPS, Prolog, Java, C & C++. For the JESS binding,
we simply extended our BasicAgent class (in Java) and added a JessEngine class
to it. At the CORBA interface side, any incoming messages are simply sent down
to the JessEngine object, which then processes it as normal (i.e. the JessEngine
object is unaware that any CORBA distribution exists). The separation of
"distribution aware" and "distribution unaware" agents is a very useful: the
JessEngine object of an intelligent agent simply knows that it should conform to
an addressing scheme when it wants to send messages out, and is guaranteed that
it will receive messages from other agents in the system.
wrt the OMG, it recently formed an agent working group, under the Internet SIG.
You should take a look at FIPA (drogo.cselt.it/fipa) to see how they have
designed agent systems (including platform management, interoperability, ACL,
and content language encoding schema).
I hope this is of some use in your design,
Dave.
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
