System Name: DIET Agents
Current Version: 0.92
Organization: BT Exact
Entry status: authoritative
Supported platforms:
Any
Supported languages:
Java
Implemented standards: none
Type of migration:
weak
How many threads or processes are possible per agent? 1
Local communication mechanisms and format of data:
Asynchronous messaging. Free format of data (text string plus optional object)
Global communication mechanisms:
Through agent migration (using TCP/IP as underlying mechanism). Several different schemes supported: e.g. Carriers and Mirrors. Also support for lightweight UDP communication.
How the communication partner can be addressed:
Platform specific naming scheme, using binary family and name tags.
Resource access control mechanism:
none by default, but can be built on top
Agent tracking:
none built into platform, but can be added
Directory of services:
none built into platform, but can be added
Type of code migration:
none
Other special features:
* Agents are very lightweight (over 100,000 agents can run on a normal desktop machine).
* A minimal, bottom-up design is used to ensure that the platform is robust, scalable, adaptive and extensible.
* The kernel functions are fail-fast and resource constrained.
Availability:
source and binary
License terms:
GNU copyleft
Article that describe the current system best:
"Core Specification and Experiments in DIET: A Decentralised Ecosystem-inspired Mobile Agent System", C. Hoile, F. Wang, E. Bonsma and P. Marrow, Proc. 1st Int. Conf. on Autonomous Agents and Multi-Agent Systems (AAMAS2002), pp. 623-630, July 2002, Bologna, Italy.
Year of first publication of systems description: 2001
Project URL: http://diet-agents.sourceforge.net
Contacts Email Address: mailbox2.to.catch22@spamgourmet.com
Last modification date of this entry: Mon Oct 20 18:34:22 MET DST 2003