Agent-oriented programming - Revision history

Frap: /* PADE (Python Agent DEvelopment framework) */ PEP-8

2025-02-10T13:21:11Z

PADE (Python Agent DEvelopment framework): PEP-8

← Previous revision		Revision as of 13:21, 10 February 2025
Line 86:		Line 86:
	def __init__(self, aid):		def __init__(self, aid):
	super(AgenteHelloWorld, self).__init__(aid=aid)		super(AgenteHelloWorld, self).__init__(aid=aid)
	display_message(self.aid.localname, 'Hello World!')		display_message(self.aid.localname, "Hello World!")
	</syntaxhighlight>		</syntaxhighlight>

105.120.131.74: /* OKEAMAH */

2024-10-09T20:18:24Z

OKEAMAH

← Previous revision		Revision as of 20:18, 9 October 2024
Line 34:		Line 34:

	=== JADE ===		=== JADE ===
	For the Java-platform one of the frameworks is [https://web.archive.org/web/20100621141053/http://jade.tilab.com/ JADE].<ref>{{cite conference\|last=Bellifeminee\|first=Fabio\|author2=Agostino Poggi \|author3=Giovanni Rimassa\|title=JADE: a FIPA2000 compliant agent development environment\|year=~~2001~~\|conference=Proceedings of the fifth international conference on Autonomous agents\|pages=216–217\|doi=10.1145/375735.376120}}</ref>		For the Java-platform one of the frameworks is [https://web.archive.org/web/20100621141053/http://jade.tilab.com/ JADE].<ref>{{cite conference\|last=Bellifeminee\|first=Fabio\|author2=Agostino Poggi \|author3=Giovanni Rimassa\|title=JADE: a FIPA2000 compliant agent development environment\|year=2024\|conference=Proceedings of the fifth international conference on Autonomous agents\|pages=216–217\|doi=10.1145/375735.376120}}</ref>
	Here is a very basic example<ref>{{cite web \|url=http://rootdev.nl/blog/article/aop_jade_configure_in_eclipse_and_netbeans \|title=Rootdev \|website=rootdev.nl \|access-date=18 September 2022 \|archive-url=https://web.archive.org/web/20110702083510/http://rootdev.nl/blog/article/aop_jade_configure_in_eclipse_and_netbeans \|archive-date=2 July 2011 \|url-status=dead}}</ref> of an agent that runs code.		Here is a very basic example<ref>{{cite web \|url=http://rootdev.nl/blog/article/aop_jade_configure_in_eclipse_and_netbeans \|title=Rootdev \|website=rootdev.nl \|access-date=18 September 2022 \|archive-url=https://web.archive.org/web/20110702083510/http://rootdev.nl/blog/article/aop_jade_configure_in_eclipse_and_netbeans \|archive-date=2 July 2011 \|url-status=dead}}</ref> of an agent that runs code.
	<syntaxhighlight lang="java">		<syntaxhighlight lang="java">

Sprhodes: /* Agent Speak (Jason) */

2024-05-17T17:10:35Z

Agent Speak (Jason)

← Previous revision		Revision as of 17:10, 17 May 2024
Line 56:		Line 56:

	=== Agent Speak (Jason) ===		=== Agent Speak (Jason) ===
			[[AgentSpeak]] is an agent-oriented programming language based on logic programming and the [[Belief–desire–intention_software_model\|belief–desire–intention]] (BDI) architecture.

	For a literal translation of agent-oriented concepts into a scheme unobfuscated as is JADE, behind Java and Object Orientedness, Agent Speak<ref>Anand S. Rao, 1996. AgentSpeak(L): BDI Agents Speak Out in a Logical Computable Language. Proceedings of Seventh European Workshop on Modelling Autonomous Agents in a Multi-Agent World (MAAMAW-96).</ref> (Jason) provides a "natural" language for agents.		For a literal translation of agent-oriented concepts into a scheme unobfuscated as is JADE, behind Java and Object Orientedness, Agent Speak<ref>Anand S. Rao, 1996. AgentSpeak(L): BDI Agents Speak Out in a Logical Computable Language. Proceedings of Seventh European Workshop on Modelling Autonomous Agents in a Multi-Agent World (MAAMAW-96).</ref> (Jason) provides a "natural" language for agents.
	<syntaxhighlight lang="jade">		<syntaxhighlight lang="jade">

Mathnerd314159: change paradigms template to navbox (see Template talk:Programming paradigms#too long)

2024-02-01T23:08:56Z

change paradigms template to navbox (see Template talk:Programming paradigms#too long)

← Previous revision		Revision as of 23:08, 1 February 2024
Line 1:		Line 1:
	{{short description\|Programming paradigm}}		{{short description\|Programming paradigm}}
	{{Multi-agent system}}		{{Multi-agent system}}
⚫	{{Programming paradigms}}
	'''Agent-oriented programming''' ('''AOP''') is a [[programming paradigm]] where the construction of the software is centered on the concept of [[software agent]]s. In contrast to [[object-oriented programming]] which has objects (providing methods with variable parameters) at its core, AOP has externally specified agents (with interfaces and messaging capabilities) at its core. They can be thought of as abstractions of objects. Exchanged messages are interpreted by receiving "agents", in a way specific to its class of agents.		'''Agent-oriented programming''' ('''AOP''') is a [[programming paradigm]] where the construction of the software is centered on the concept of [[software agent]]s. In contrast to [[object-oriented programming]] which has objects (providing methods with variable parameters) at its core, AOP has externally specified agents (with interfaces and messaging capabilities) at its core. They can be thought of as abstractions of objects. Exchanged messages are interpreted by receiving "agents", in a way specific to its class of agents.

Line 99:		Line 98:
	== References ==		== References ==
	{{Reflist}}		{{Reflist}}

		⚫	{{Programming paradigms navbox}}

	{{DEFAULTSORT:Agent-Oriented Programming}}		{{DEFAULTSORT:Agent-Oriented Programming}}

153.19.32.205 at 15:28, 17 January 2024

2024-01-17T15:28:04Z

← Previous revision		Revision as of 15:28, 17 January 2024
Line 2:		Line 2:
	{{Multi-agent system}}		{{Multi-agent system}}
	{{Programming paradigms}}		{{Programming paradigms}}
	'''Agent-oriented programming''' ('''AOP''') is a [[programming paradigm]] where the construction of the software is centered on the concept of [[software agent]]s. In contrast to [[object-oriented programming]] which has objects (providing methods with variable parameters) at its core, AOP has externally specified agents (with interfaces and messaging capabilities) at its core. They can be thought of as abstractions of objects. Exchanged messages are interpreted by receiving "agents", in a way specific to its class of ~~agents. It may also mean James Bond game about~~ agents.		'''Agent-oriented programming''' ('''AOP''') is a [[programming paradigm]] where the construction of the software is centered on the concept of [[software agent]]s. In contrast to [[object-oriented programming]] which has objects (providing methods with variable parameters) at its core, AOP has externally specified agents (with interfaces and messaging capabilities) at its core. They can be thought of as abstractions of objects. Exchanged messages are interpreted by receiving "agents", in a way specific to its class of agents.

	== History ==		== History ==

153.19.32.205 at 15:27, 17 January 2024

2024-01-17T15:27:01Z

← Previous revision		Revision as of 15:27, 17 January 2024
Line 2:		Line 2:
	{{Multi-agent system}}		{{Multi-agent system}}
	{{Programming paradigms}}		{{Programming paradigms}}
	'''Agent-oriented programming''' ('''AOP''') is a [[programming paradigm]] where the construction of the software is centered on the concept of [[software agent]]s. In contrast to [[object-oriented programming]] which has objects (providing methods with variable parameters) at its core, AOP has externally specified agents (with interfaces and messaging capabilities) at its core. They can be thought of as abstractions of objects. Exchanged messages are interpreted by receiving "agents", in a way specific to its class of agents.		'''Agent-oriented programming''' ('''AOP''') is a [[programming paradigm]] where the construction of the software is centered on the concept of [[software agent]]s. In contrast to [[object-oriented programming]] which has objects (providing methods with variable parameters) at its core, AOP has externally specified agents (with interfaces and messaging capabilities) at its core. They can be thought of as abstractions of objects. Exchanged messages are interpreted by receiving "agents", in a way specific to its class of agents. It may also mean James Bond game about agents.

	== History ==		== History ==

Jerryobject: /* History */ Small WP:COPYEDIT WP:EoS WP:TERSE: parallelism (grammar). Template:Blockquote add.

2023-09-26T11:42:58Z

History: Small WP:COPYEDIT WP:EoS WP:TERSE: parallelism (grammar). Template:Blockquote add.

← Previous revision		Revision as of 11:42, 26 September 2023
Line 8:		Line 8:
	{{cite book \|first=Y. \|last=Shoham \|year=1990 \|title=Agent-Oriented Programming \|publisher=Computer Science Department \|location=Stanford University \|type=Technical Report STAN-CS-90-1335}}</ref><ref>		{{cite book \|first=Y. \|last=Shoham \|year=1990 \|title=Agent-Oriented Programming \|publisher=Computer Science Department \|location=Stanford University \|type=Technical Report STAN-CS-90-1335}}</ref><ref>
	{{cite journal \|last=Shoham \|first=Y. \|year=1993 \|title=Agent-Oriented Programming \|journal=Artificial Intelligence \|citeseerx =10.1.1.123.5119 \|pages=51–92 \|volume=60 \|issue=1 \|doi=10.1016/0004-3702(93)90034-9}}		{{cite journal \|last=Shoham \|first=Y. \|year=1993 \|title=Agent-Oriented Programming \|journal=Artificial Intelligence \|citeseerx =10.1.1.123.5119 \|pages=51–92 \|volume=60 \|issue=1 \|doi=10.1016/0004-3702(93)90034-9}}
	</ref> His agents are specific to his own paradigm as they have ~~just~~ one method, with ~~a single~~ parameter. To quote Yoav Shoham from his paper in 1990 for a basic difference between AOP and OOP:		</ref> His agents are specific to his own paradigm as they have only one method, with one parameter. To quote Yoav Shoham from his paper in 1990 for a basic difference between AOP and OOP:
	:...agent-oriented programming (AOP), which can be viewed as a specialization of object-oriented programming. ~~...~~		{{Blockquote\|... agent-oriented programming (AOP), which can be viewed as a specialization of object-oriented programming.}}

	{\| class="wikitable plainrowheaders"		{\| class="wikitable plainrowheaders"

Jerryobject: Nonlead-word proper + nonproper noun MOS:CAPS > WP:LOWERCASE sentence case. WP:LINK update-standardize. WP:REFerence WP:CITation parameters: respaces, reorders, update-standardizes, conform to master templates. Cut needless carriage return whitespace character in section: to standardize, aid work via small screens.

2023-09-26T11:23:20Z

Nonlead-word proper + nonproper noun MOS:CAPS > WP:LOWERCASE sentence case. WP:LINK update-standardize. WP:REFerence WP:CITation parameters: respaces, reorders, update-standardizes, conform to master templates. Cut needless carriage return whitespace character in section: to standardize, aid work via small screens.

← Previous revision		Revision as of 11:23, 26 September 2023
Line 5:		Line 5:

	== History ==		== History ==
	Historically, the concept of agent-oriented programming and the idea of centering software around the concept of an Agent was introduced by [[Yoav Shoham]] within his [[~~Artificial~~ ~~Intelligence~~]] studies in 1990.<ref>		Historically, the concept of agent-oriented programming and the idea of centering software around the concept of an Agent was introduced by [[Yoav Shoham]] within his [[artificial intelligence]] studies in 1990.<ref>
	{{cite book \| first=Y. \| last=Shoham \| year=1990 \| title=Agent-Oriented Programming \| publisher = Computer Science Department \| location = Stanford University \| type = Technical Report STAN-CS-90-1335}}</ref><ref>		{{cite book \|first=Y. \|last=Shoham \|year=1990 \|title=Agent-Oriented Programming \|publisher=Computer Science Department \|location=Stanford University \|type=Technical Report STAN-CS-90-1335}}</ref><ref>
	{{cite journal \| first=Y. \| ~~last=Shoham \|~~ year=1993 \| title=Agent-Oriented Programming \| journal = Artificial Intelligence \| ~~volume=60 \|~~ citeseerx =10.1.1.123.5119 \| pages = ~~51–92~~ \| doi = 10.1016/0004-3702(93)90034-9 ~~\| issue = 1~~}}		{{cite journal \|last=Shoham \|first=Y. \|year=1993 \|title=Agent-Oriented Programming \|journal=Artificial Intelligence \|citeseerx =10.1.1.123.5119 \|pages=51–92 \|volume=60 \|issue=1 \|doi=10.1016/0004-3702(93)90034-9}}
	</ref> His agents are specific to his own paradigm as they have just one method, with a single parameter. To quote Yoav Shoham from his paper in 1990 for a basic difference between AOP and OOP:		</ref> His agents are specific to his own paradigm as they have just one method, with a single parameter. To quote Yoav Shoham from his paper in 1990 for a basic difference between AOP and OOP:
	:...agent-oriented programming (AOP), which can be viewed as a specialization of object-oriented programming. ...		:...agent-oriented programming (AOP), which can be viewed as a specialization of object-oriented programming. ...
Line 68:		Line 68:

	=== SARL Language ===		=== SARL Language ===
	[[SARL (programming language)\|SARL]]<ref>{{cite book\|~~doi~~=~~10.1109/wi-iat.~~2014~~.156~~\|chapter=SARL: A General-Purpose Agent-Oriented Programming Language\|title=2014 IEEE/WIC/ACM International Joint Conferences on Web Intelligence (WI) and Intelligent Agent Technologies (IAT)\|pages=103–110\|~~year~~=2014~~\|last1=Rodriguez\|first1=Sebastian\|last2=Gaud\|first2=Nicolas\|last3=Galland\|first3=Stéphane~~\|isbn=978-1-4799-4143-8\|s2cid=15508257 }}</ref> provides the fundamental abstractions for coding multiagent systems.<ref>[http://www.sarl.io SARL website]</ref> It uses a script-like syntax (inspired by Scala and Ruby).		[[SARL (programming language)\|SARL]]<ref>{{cite book \|last1=Rodriguez \|first1=Sebastian \|last2=Gaud \|first2=Nicolas \|last3=Galland \|first3=Stéphane \|year=2014 \|chapter=SARL: A General-Purpose Agent-Oriented Programming Language \|title=2014 IEEE/WIC/ACM International Joint Conferences on Web Intelligence (WI) and Intelligent Agent Technologies (IAT) \|pages=103–110 \|doi=10.1109/wi-iat.2014.156 \|isbn=978-1-4799-4143-8 \|s2cid=15508257}}</ref> provides the fundamental abstractions for coding multiagent systems.<ref>[http://www.sarl.io SARL website]</ref> It uses a script-like syntax (inspired by Scala and Ruby).
	<syntaxhighlight lang="sarl">		<syntaxhighlight lang="sarl">
	package helloworld		package helloworld
Line 80:		Line 80:

	=== PADE (Python Agent DEvelopment framework) ===		=== PADE (Python Agent DEvelopment framework) ===
	PADE<ref>{{cite web \| url=https://pade.readthedocs.io/en/latest/index.html \| title=Python Agent DEvelopment framework — Pade 1.0 documentation }}</ref> is a python package to develop intelligent agents in python language. This framework complies to FIPA and ACL standards.		PADE<ref>{{cite web \|url=https://pade.readthedocs.io/en/latest/index.html \|title=Python Agent DEvelopment framework — Pade 1.0 documentation}}</ref> is a python package to develop intelligent agents in python language. This framework complies to FIPA and ACL standards.
	<syntaxhighlight lang="python">		<syntaxhighlight lang="python">
	class AgenteHelloWorld(Agent):		class AgenteHelloWorld(Agent):
Line 89:		Line 89:

	== Middleware ==		== Middleware ==
	One way to implement modular or extensible AOP support is to define standard AOP [[API]]s to [[middleware]] functions that are themselves implemented as [[software agent]]s. For example, a directory service can be implemented as a [[Foundation for Intelligent Physical Agents\|FIPA]] directory facilitator or DF software agent; life-cycle management to start, stop, suspend and resume agents can be implemented as a FIPA Agent Management Service or AMS agent.<ref>{{cite journal\|last=Poslad\|first=S\|title=Specifying Protocols for Multi-agent System Interaction\|year=2007\|journal=ACM Transactions on Autonomous and Adaptive Systems\|volume=2\|issue=4\|pages=15–es\|doi=10.1145/1293731.1293735\|s2cid=9477595}}</ref> A benefit of the AOP approach is that it supports more dynamic roles between different users and providers of applications, services and networks. For example, traditionally, networks and services were usually managed by the network and service provider on behalf of the customer and offered as a single virtual network service but customers themselves are becoming more empowered to integrate and manage their own services. This can be achieved via AOP and APIs to middleware agents that can flexibly and dynamically manage communication.<ref>{{cite book\|~~last~~=Poslad\|~~first~~=S\|~~author2~~=J. ~~Pitt~~ \|~~author3~~=A. ~~Mamdani~~ \|~~author4~~=R. ~~Hadingham~~ \|~~author5~~=P. ~~Buckle~~ \|title = Agent-oriented middleware for integrating customer network services. In: Software Agents for Future Communication Systems, Hayzelden A, Bigham J ~~Eds~~.\| year = 1999\|pages=221–242\|doi=10.1007/978-3-642-58418-3_9}}</ref>		One way to implement modular or extensible AOP support is to define standard AOP [[API]]s to [[middleware]] functions that are themselves implemented as [[software agent]]s. For example, a directory service can be implemented as a [[Foundation for Intelligent Physical Agents\|FIPA]] directory facilitator or DF software agent; life-cycle management to start, stop, suspend and resume agents can be implemented as a FIPA Agent Management Service or AMS agent.<ref>{{cite journal\|last=Poslad\|first=S\|title=Specifying Protocols for Multi-agent System Interaction\|year=2007\|journal=ACM Transactions on Autonomous and Adaptive Systems\|volume=2\|issue=4\|pages=15–es\|doi=10.1145/1293731.1293735\|s2cid=9477595}}</ref> A benefit of the AOP approach is that it supports more dynamic roles between different users and providers of applications, services and networks. For example, traditionally, networks and services were usually managed by the network and service provider on behalf of the customer and offered as a single virtual network service but customers themselves are becoming more empowered to integrate and manage their own services. This can be achieved via AOP and APIs to middleware agents that can flexibly and dynamically manage communication.<ref>{{cite book \|last1=Poslad \|first1=S. \|last2=Pitt \|first2=J. \|last3=Mamdani \|first3=A. \|last4=Hadingham \|first4=R. \|last5=Buckle \|first5=P. \|title=Agent-oriented middleware for integrating customer network services. In: Software Agents for Future Communication Systems \|editor1-last=Hayzelden \|editor1-first=A. \|editor2-last=Bigham \|editor2-first=J. \|year=1999 \|pages=221–242 \|doi=10.1007/978-3-642-58418-3_9}}</ref>

	== See also ==		== See also ==

	* {{Annotated link \|Software agent}}		* {{Annotated link \|Software agent}}
	* {{Annotated link \|NetLogo}}		* {{Annotated link \|NetLogo}}

Citation bot: Add: title. Changed bare reference to CS1/2. | Use this bot. Report bugs. | Suggested by Mako001 | Linked from User:Mako001/Accesdatewithouturl3 | #UCB_webform_linked 14/2079

2023-04-16T04:35:11Z

Add: title. Changed bare reference to CS1/2. | Use this bot. Report bugs. | Suggested by Mako001 | Linked from User:Mako001/Accesdatewithouturl3 | #UCB_webform_linked 14/2079

← Previous revision		Revision as of 04:35, 16 April 2023
Line 80:		Line 80:

	=== PADE (Python Agent DEvelopment framework) ===		=== PADE (Python Agent DEvelopment framework) ===
	PADE<ref>https://pade.readthedocs.io/en/latest/index.html</ref> is a python package to develop intelligent agents in python language. This framework complies to FIPA and ACL standards.		PADE<ref>{{cite web \| url=https://pade.readthedocs.io/en/latest/index.html \| title=Python Agent DEvelopment framework — Pade 1.0 documentation }}</ref> is a python package to develop intelligent agents in python language. This framework complies to FIPA and ACL standards.
	<syntaxhighlight lang="python">		<syntaxhighlight lang="python">
	class AgenteHelloWorld(Agent):		class AgenteHelloWorld(Agent):

Citation bot: Add: s2cid. | Use this bot. Report bugs. | Suggested by Whoop whoop pull up | #UCB_webform 53/391

2023-03-27T20:52:11Z

Add: s2cid. | Use this bot. Report bugs. | Suggested by Whoop whoop pull up | #UCB_webform 53/391

← Previous revision		Revision as of 20:52, 27 March 2023
Line 68:		Line 68:

	=== SARL Language ===		=== SARL Language ===
	[[SARL (programming language)\|SARL]]<ref>{{cite book\|doi=10.1109/wi-iat.2014.156\|chapter=SARL: A General-Purpose Agent-Oriented Programming Language\|title=2014 IEEE/WIC/ACM International Joint Conferences on Web Intelligence (WI) and Intelligent Agent Technologies (IAT)\|pages=103–110\|year=2014\|last1=Rodriguez\|first1=Sebastian\|last2=Gaud\|first2=Nicolas\|last3=Galland\|first3=Stéphane\|isbn=978-1-4799-4143-8}}</ref> provides the fundamental abstractions for coding multiagent systems.<ref>[http://www.sarl.io SARL website]</ref> It uses a script-like syntax (inspired by Scala and Ruby).		[[SARL (programming language)\|SARL]]<ref>{{cite book\|doi=10.1109/wi-iat.2014.156\|chapter=SARL: A General-Purpose Agent-Oriented Programming Language\|title=2014 IEEE/WIC/ACM International Joint Conferences on Web Intelligence (WI) and Intelligent Agent Technologies (IAT)\|pages=103–110\|year=2014\|last1=Rodriguez\|first1=Sebastian\|last2=Gaud\|first2=Nicolas\|last3=Galland\|first3=Stéphane\|isbn=978-1-4799-4143-8\|s2cid=15508257 }}</ref> provides the fundamental abstractions for coding multiagent systems.<ref>[http://www.sarl.io SARL website]</ref> It uses a script-like syntax (inspired by Scala and Ruby).
	<syntaxhighlight lang="sarl">		<syntaxhighlight lang="sarl">
	package helloworld		package helloworld
Line 89:		Line 89:

	== Middleware ==		== Middleware ==
	One way to implement modular or extensible AOP support is to define standard AOP [[API]]s to [[middleware]] functions that are themselves implemented as [[software agent]]s. For example, a directory service can be implemented as a [[Foundation for Intelligent Physical Agents\|FIPA]] directory facilitator or DF software agent; life-cycle management to start, stop, suspend and resume agents can be implemented as a FIPA Agent Management Service or AMS agent.<ref>{{cite journal\|last=Poslad\|first=S\|title=Specifying Protocols for Multi-agent System Interaction\|year=2007\|journal=ACM Transactions on Autonomous and Adaptive Systems\|volume=2\|issue=4\|pages=15–es\|doi=10.1145/1293731.1293735}}</ref> A benefit of the AOP approach is that it supports more dynamic roles between different users and providers of applications, services and networks. For example, traditionally, networks and services were usually managed by the network and service provider on behalf of the customer and offered as a single virtual network service but customers themselves are becoming more empowered to integrate and manage their own services. This can be achieved via AOP and APIs to middleware agents that can flexibly and dynamically manage communication.<ref>{{cite book\|last=Poslad\|first=S\|author2=J. Pitt \|author3=A. Mamdani \|author4=R. Hadingham \|author5=P. Buckle \|title = Agent-oriented middleware for integrating customer network services. In: Software Agents for Future Communication Systems, Hayzelden A, Bigham J Eds.\| year = 1999\|pages=221–242\|doi=10.1007/978-3-642-58418-3_9}}</ref>		One way to implement modular or extensible AOP support is to define standard AOP [[API]]s to [[middleware]] functions that are themselves implemented as [[software agent]]s. For example, a directory service can be implemented as a [[Foundation for Intelligent Physical Agents\|FIPA]] directory facilitator or DF software agent; life-cycle management to start, stop, suspend and resume agents can be implemented as a FIPA Agent Management Service or AMS agent.<ref>{{cite journal\|last=Poslad\|first=S\|title=Specifying Protocols for Multi-agent System Interaction\|year=2007\|journal=ACM Transactions on Autonomous and Adaptive Systems\|volume=2\|issue=4\|pages=15–es\|doi=10.1145/1293731.1293735\|s2cid=9477595}}</ref> A benefit of the AOP approach is that it supports more dynamic roles between different users and providers of applications, services and networks. For example, traditionally, networks and services were usually managed by the network and service provider on behalf of the customer and offered as a single virtual network service but customers themselves are becoming more empowered to integrate and manage their own services. This can be achieved via AOP and APIs to middleware agents that can flexibly and dynamically manage communication.<ref>{{cite book\|last=Poslad\|first=S\|author2=J. Pitt \|author3=A. Mamdani \|author4=R. Hadingham \|author5=P. Buckle \|title = Agent-oriented middleware for integrating customer network services. In: Software Agents for Future Communication Systems, Hayzelden A, Bigham J Eds.\| year = 1999\|pages=221–242\|doi=10.1007/978-3-642-58418-3_9}}</ref>

	== See also ==		== See also ==