Home | Trees | Indices | Help |
|
---|
|
object --+ | Registrations
All calls may result in access/modifications to node registrations dictionary, so be careful to guarantee appropriate thread-safeness.
Data structure for storing a set of registrations (e.g. publications, services). The underlying data storage is the same except for services, which have the constraint that only one registration may be active for a given key.
Instance Methods | |||
|
|||
|
|||
|
|||
|
|||
[str] |
|
||
|
|||
[(str, str),] |
|
||
bool |
|
||
[str, [str]...] |
|
||
|
|||
|
|||
code, msg, val |
|
||
Inherited from |
Class Variables | |
TOPIC_SUBSCRIPTIONS = 1
|
|
TOPIC_PUBLICATIONS = 2
|
|
SERVICE = 3
|
|
PARAM_SUBSCRIPTIONS = 4
|
Properties | |
Inherited from |
Method Details |
ctor.
|
|
Iterate over registration keys
|
Lookup service API URI. NOTE: this should only be valid if type==SERVICE as service Registrations instances are the only ones that track service API URIs.
|
Only valid if self.type != SERVICE.
|
|
|
|
Add caller_id into the map as a provider of the specified service (key). caller_id must not have been previously registered with a different caller_api. Subroutine for managing provider map data structure (essentially a multimap).
|
Remove all registrations associated with caller_id
|
Remove caller_id from the map as a provider of the specified service (key). Subroutine for managing provider map data structure, essentially a multimap
|
Home | Trees | Indices | Help |
|
---|
Generated by Epydoc 3.0.1 on Sat Mar 2 13:23:39 2013 | http://epydoc.sourceforge.net |