Part of bzrlib.transport View In Hierarchy
A registration of a new protocol requires two steps: 1) register the prefix with the function register_transport( ) 2) register the protocol provider with the function register_transport_provider( ) ( and the "lazy" variant )
This is needed because: a) a single provider can support multiple protocols ( like the ftp provider which supports both the ftp:// and the aftp:// protocols ) b) a single protocol can have multiple providers ( like the http:// protocol which is supported by both the urllib and pycurl provider )
Method | register_transport_provider | Undocumented |
Method | register_lazy_transport_provider | Undocumented |
Method | register_transport | Undocumented |
Inherited from Registry:
Method | __init__ | Create a new Registry. |
Method | register | Register a new object to a name. |
Method | register_lazy | Register a new object to be loaded on request. |
Method | get | Return the object register()'ed to the given key. |
Method | get_prefix | Return an object whose key is a prefix of the supplied value. |
Method | get_help | Get the help text associated with the given key |
Method | get_info | Get the extra information associated with the given key |
Method | remove | Remove a registered entry. |
Method | __contains__ | Undocumented |
Method | keys | Get a list of registered entries |
Method | iteritems | Undocumented |
Method | items | Undocumented |
Method | _add_help_and_info | Add the help and information about this key |
Method | _get_module | Return the module the object will be or was loaded from. |
Method | _get_key_or_default | Return either 'key' or the default key if key is None |
Method | _set_default_key | Undocumented |
Method | _get_default_key | Undocumented |