OPC UA xRegistry generic server-side registry node managers: content-addressed resource resolution (Opaque NodeId fast path), the CreateResource/Write/Close registration lifecycle, and federation.
Install
| Product | Versions |
|---|---|
| .NET | |
| .NET Standard | |
| Other |
README
Opc.Ua.XRegistry.Server
The generic server-side xRegistry registry node managers for OPC UA. They serve a content-addressed resource registry in a server address space:
- Fast path — publishes registered resources under an Opaque NodeId whose Identifier is
the raw content-id bytes, so a consumer resolves a resource in a single
Read. - Registration — the model's own lifecycle:
CreateGroup/GetOrCreateGroupon the registry root,CreateResource/GetOrCreateResourceon a group, and — becauseResourceTypeis aFileType— the document is transferred with the inheritedOpen/Read/Write/Close. On close the server computes the resource's content-derived id (via anIResourceContentIdProvider) and publishes the Opaque fast-path node at runtime.Delete(ExpectedEpoch)gives optimistic concurrency on removal. - Federation — publishes a proxy for a resource hosted by a remote registry as a real
ResourceTypeinstance carrying anExternalReferenceandResourceUrlplus the content-derived id (stable across registries).
Document bytes live behind an injectable IXRegistryResourceStore; an in-process and a
file-backed implementation ship with the package. Registry writes always require a
SignAndEncrypt secure channel.
A concrete registry (for example a schema registry) supplies an
IResourceContentIdProvider and its own companion namespace/NodeSet.
Adoption Assessment
A verified publisher signal is available. Assess fit from the package's supported frameworks, license and dependency graph rather than popularity alone.
Related Guides & Workflows
Learn how to evaluate, integrate, or audit this package in your .NET project.