A (Host/Registry) node on a Qt Remote Objects network. More…
This documentation may contain snippets that were automatically translated from C++ to Python. We always welcome contributions to the snippet translation. If you see an issue with the translation, you can also let us know by creating a ticket on https:/bugreports.qt.io/projects/PYSIDE
QRemoteObjectRegistryHost has the same capability that a
QRemoteObjectHost has (which includes everything a
QRemoteObjectNode supports), and in addition is the owner of the Registry. Any
QRemoteObjectHost node that connects to this Node will have all of their Source objects made available by the Registry.
Nodes only support connection to one registry , calling
setRegistryUrl when a Registry is already set is considered an error. For something like a secure and insecure network (where different Registries would be applicable), the recommendation is to create separate Nodes to connect to each, in effect creating two independent Qt Remote Objects networks.
Nodes may connect to each other directly using
connectToNode , or they can use the
QRemoteObjectRegistry to simplify connections.
QRemoteObjectRegistry is a special Replica available to every Node that connects to the Registry Url. It knows how to connect to every QRemoteObjectSource object on the network.
- class PySide6.QtRemoteObjects.QRemoteObjectRegistryHost([registryAddress=QUrl()[, parent=None]])#
Constructs a new
QRemoteObjectRegistryHost Node with the given
parent. RegistryHost Nodes have the same functionality as
QRemoteObjectHost Nodes, except rather than being able to connect to a
QRemoteObjectRegistry , the provided Host
registryAddress) becomes the address of the registry for other Nodes to connect to.