Package jade.proto

This package contains role behaviours for FIPA standard protocols.

See: Description

Interface Summary

Interface	Description
FIPAProtocolNames	Deprecated Use jade.domain.FIPANames.InteractionProtocol instead
SubscriptionResponder.SubscriptionManager	Inner interface SubscriptionManager.
TwoPhConstants	Interface description

Class Summary

Class	Description
AchieveREInitiator	This is a single homogeneous and effective implementation of all the FIPA-Request-like interaction protocols defined by FIPA, that is all those protocols where the initiator sends a single message (i.e. it performs a single communicative act) within the scope of an interaction protocol in order to verify if the RE (Rational Effect) of the communicative act has been achieved or not.
AchieveREResponder	This is a single homogeneous and effective implementation of all the FIPA-Request-like interaction protocols defined by FIPA, that is all those protocols where the initiator sends a single message (i.e. it performs a single communicative act) within the scope of an interaction protocol in order to verify if the RE (Rational Effect) of the communicative act has been achieved or not.
ContractNetInitiator	This class implements the initiator role in a Fipa-Contract-Net or Iterated-Fipa-Contract-Net interaction protocol.
ContractNetResponder	Behaviour class for fipa-contract-net Responder role.
IteratedAchieveREInitiator	This class implements the initiator role in the iterated version of fipa-request like interaction protocols.
ProposeInitiator	This class implements the Fipa-Propose interaction protocol with an API similar and homogeneous to AchieveREInitiator.
ProposeResponder	Behaviour class for fipa-propose Responder role.
SimpleAchieveREInitiator	This is simple implementation of the AchieveREInitiator.
SimpleAchieveREResponder	This is a single homogeneous and effective implementation of all the FIPA-Request-like interaction protocols defined by FIPA, that is all those protocols where the initiator sends a single message (i.e. it performs a single communicative act) within the scope of an interaction protocol in order to verify if the RE (Rational Effect) of the communicative act has been achieved or not.
SSContractNetResponder	Single Session version of the Responder role in the Fipa-Contract-Net protocol.
SSIteratedAchieveREResponder	Single Session version of the Responder role in the Iterated-Fipa-Request protocol.
SSIteratedContractNetResponder
SSResponderDispatcher	This behaviour is designed to be used together with the Single-Session responder protocol classes.
SubscriptionInitiator	This is a single homogeneous and effective implementation of the initiator role in all the FIPA-Subscribe-like interaction protocols defined by FIPA, that is all those protocols where the initiator sends a single "subscription" message and receives notifications each time a given condition becomes true.
SubscriptionResponder	This is a single homogeneous and effective implementation of the responder role in all the FIPA-Subscribe-like interaction protocols defined by FIPA, that is all those protocols where the initiator sends a single "subscription" message and receives notifications each time a given condition becomes true.
SubscriptionResponder.Subscription	Inner calss Subscription This class represents a subscription.
TwoPh0Initiator	Class description
TwoPh1Initiator	Class description
TwoPh2Initiator	Class description
TwoPhInitiator	Class description
TwoPhResponder	Class description

Package jade.proto Description

This package contains role behaviours for FIPA standard protocols. For every interaction protocol mandated by FIPA specifications, two roles can be played by an agent:

1. Initiator role: the agent contacts one or more other agents to start up a new conversation, evolving according a specific interaction protocol.
2. Responder role: in response to a message received from some other agent, the agent carries on a new conversation following a specific interaction protocol.

JADE provides a Behaviour object for each one of these two protocol roles; these behaviours often are abstract classes that application programmers must extend in order to provide application specific code to handle the various protocol steps.