Docjar: A Java Source and Docuemnt Enginecom.*    java.*    javax.*    org.*    all    new    plug-in

Quick Search    Search Deep

alice.tuplemedium.runtime.* (22)

alice.tuplemedium: Javadoc index of package alice.tuplemedium.


Package Samples:

alice.tuplemedium.runtime

Classes:

User: this is the basic class for developing tuple media TCP/IP user. if the user is recognized to be local the interactions with the tuple centre virtual machines are realized directly, bypassing TCP/IP protocol (this is possible because of there is only one daemon service installed on a java VM). if the tuple centre is remote, this class provide the user proxy (or connector) to remote service In this case the class UserListener is the related stub or acceptor, on the remote (daemon) side.
InspectorListener: this is inspector active acceptor class receiving communication events from user proxy and dispatching them to the referenced tuple centre virtual machine. The interaction is bidirectional: output events from tuple centre vm are dispatched to user proxy. the inspector acceptor observe specific tuple centre events according to the current inspector protocol the inspector implements ObservableEventListener in order to observe tuple centre observable events
Event: Represents internal events of the tuple centre virtual machine According to the tuple centre model, an event is characterised by the operation which caused the event, the tuple or the tuple template as information content of the operation, the direction of the event (from agent to the tuple centre, or viceversa), the identification of the agent responsible of the operation, the identification of the tuple centre where the event has happened.
Inspector: this is the basic class for developing tuple media TCP/IP inspector. as users, inspectors are active agents built with acceptor/connector pattern this class represents the proxy or connector however, different from user, an inspector proxy is connected to only one specific tuple centre inspector can observe a set of events and information described in Inspector Protocol
TupleCentreVM: Defines the core behaviour of a tuple centre virtual machine. The behaviour reflects the operational semantic expressed in related tuple centre articles. It is abstract because it not specifies how the output events are dispatched. Note that in order to specify a concrete virtual machine, concrete object implementing TupleSet, EventSet, TRSet, Reactor, Reaction must be specified.
Daemon: Daemon class implement the basic behaviour of an TCP/IP infrastructure which listens for new tuple media clients, creates new tuple media, creates client request acceptors. it's the basic component from which derives the infrastructure topology the class has been designed as Singleton pattern: for each java VM only ONE Daemon could be installed
TRSet: Specifies the services which must be provided by the component inside the tuple centre virtual machine collecting and managing triggered reactions as a multiset An important aspect of the component implementing this interface is the ability to execute transactions, that is execute sequence of operations that could be commited or asked to be undone.
UserListener: this is user active acceptor class receiving communication events from user proxy and dispatching them to the referenced tuple centre virtual machine. The interaction is bidirectional: output events from tuple centre vm are dispatched to user proxy an acceptor could serve more then one user proxy (because of it hasn't blocking operations)
TupleSet: Specifies the services which must be provided by the component inside the tuple centre virtual machine collecting and managing tuples as a multiset An important aspect of the component implementing this interface is the ability to execute transactions, that is execute sequence of operations that could be commited or asked to be undone.
EventOperation: Defines the possible operation types which caused an tuple centre virtual machine event, according to the coordination language of the tuple medium The string representation of the operation involves the name of the operation and the number of argument it requires.
TupleCentreVMImpl: This class extends base virtual machine core in order to make the tuple centre reachable with a proper interface and specifying a way to dispatch output events.The concept of VMListener is introduced to identify targets of output communication events.
Reactor: Defines the tuple centre reactive behaviour, which is the core of its coordination ability. It manages reactions which are triggered by internal and external communication events and executed. See literature about tuple centre model for details.
TupleTemplate: Defines the template used to retrieve tuple information from Tuple Centres, thorugh interactions. So TupleTemplate identifies a set of tuples. With Tuple, it's the basic interfaces defining the communication language of tuple centre model.
Reaction: Represents the reaction concept of tuple centre model. Reactions are computations executed inside tuple centres, triggered by external and internal communication events (which depends on the specific tuple centre model).
EventDirection: this class defines the direction of a tuple centre event from virtual machine to outside, with success from virtual machine to outside, with failure from outside to virtual machine
Tuple: Defines the information content of tuple centre and exchanged thorugh interactions. With TupleTemplate, it's the basic interfaces defining the communication language of tuple centre model.
AgentId: Represents an agent identifier It's used inside tuple centre to identify an agent interacting with the medium. Note that the model doesn't specify any specific id structure.
InvalidTupleTemplateException: This exception is thrown when a not well-formed tuple template is found, for instance when invoking a coordination language primitive with a null tuple template.
EventSet: Specifies the services which must be provided by component inside tuple centre virtual machine that manages communication events as a multiset
InvalidTupleException: This exception is thrown when a not well-formed tuple is found, for instance when invoking a coordination language primitive with a null tuple.
VMListener: Defines the services that must be provided by any object which must receive commounication output events produced by a tuple centre
NewInspectorMsg: message sent by an inspector to a daemon in order to become an (inspector) user of a tuple centre
NoDaemonException: Exception thrown when trying to interact with a node (host) where the daemon is not installed
NodeMsg: base class for message requesting a service from a user or inspector to a tuple centre node
UnknownMediumException: Exception thrown when trying to install a daemon with coordination medium of unknown class

Home | Contact Us | Privacy Policy | Terms of Service