Home >> All >> alice >> tuplemedium >> [ runtime Javadoc ]

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


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
• 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
• 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
• 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)
• 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
• InspectorConnectionInfo: information about an established connection with the remote tuple centre virtual machine
• UserConnectionInfo: information about an established connection with a remote tuple centre virtual machine
• CommunicationEventMsg: msg containing a service request (in,out,rd,..) from the user to a tuple centre
• PortNotAvailableException: Exception thrown when trying to install a daemon on a TCP/IP port already bound
• NewUserMsg: message sent by a user to a daemon in order to become user of a tuple centre
• NextStepMsg: inspector message to ask a new execution step for a traced tuple centre vm
• SetEventSetMsg: inspector message to set a new event Wn set in the observed tuple centre
• SetTupleSetMsg: inspector message to set a new tuple set in the observed tuple centre
• InspectorMsg: message from inspector connector (proxy) to inspector acceptor
• InspectorProtocol: this class defines the observation protocol of inspectors
• PingMsg: message sent to check the presence of a tuple medium node
• ResetMsg: inspector message to reset the observed tuple centre vm
• SetProtocolMsg: inspector message to set a new observation protocol
• ShutdownMsg: message indicating that a user has shutdown
• GetSnapshotMsg

Home | Contact Us | Privacy Policy | Terms of Service