/ . / Collaboratory / Node.py / NodeServerImplementation
After the node initially connects to the Hub,
the hub makes a back-connection to the node
The Node Server waits for commands from the Hub
then pushes them to Chimera
Methods
|
|
|
receive_messages_from_hub
|
receive_messages_from_hub ( self, messages )
receive a command from the Hub Client
place it on the queue so that the Node GUI can apply it
|
|
determine_base_id
|
determine_base_id ( self )
determine the base id that the Collaboratory should start counting
objects from. This is to account for several objects (Camera, MaterialColors)
that the Collaboratory knows about upon startup
|
|
query_state
|
query_state ( self )
Just a dummy function that allows the Hub to try to back connect to Node, to see if
there are any connection issues
|
|
setActivePpt
|
setActivePpt ( self, name )
Hub directly calls this function to tell Node to set a certain user to be the active participant
i.e. so they'll have an asterisk next to their name
Perhaps this should be encapsulated in a CORBA message, instead of a direct call?
|
|
killMe
|
killMe ( self )
Function can be called by the Hub to terminate this node. This would happen in several cases.
(1) If the node has gone down, say due to network error.
(2) If the hub is shutting down, and needs to disconnect all of the connected participants.
|
|
setReplyObj
|
setReplyObj ( self, info )
Because GUI elements can only be altered from the main thread, this helper function
sets a variable in the chimera interactor that is checked by the main thread
|
|
__init__
|
__init__ (
self,
object_queue,
parent,
)
|
|
|