Skip to content
zero-objectsPublic

About

OSS DDS implementation in Rust

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

20 stars

Watchers

3 watching

Forks

Latest commit

 

History

270 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

ZeroDDS

License Rust Edition

ZeroDDS is a Rust implementation of OMG DDS, with language bindings, code generation and protocol bridges in one source workspace.

Source status: RC7 preparation. This checkout is not release approval or a statement that RC7 crates, installers and container images are published. The instructions below follow this source revision. External channels can still describe an earlier release.

Evidence and scope

Interop is evaluated per case, representation, direction and toolchain. A successful case is not a promise that all constructs or configurations interoperate, and successful round trips do not imply identical bytes.

The interop ledger presents the measurements. The recorded results and specification coverage sources retain their own scope and revision. Historical checklist totals are not a whole-product RC7 conformance certificate. See the case evidence before extrapolating a result to a deployment.

The repository still documents its Vendor-ID as provisional. The RTPS source is the authority for the emitted identifier, not an inferred OMG registration. This README does not assert that a Vendor-ID is the only possible cross-vendor difference.

Quickstart from this checkout

Use Rust 1.97 or newer and a native linker. From the checkout root:

cargo build --locked -j 1 -p zerodds-dcps \
  --example hello_dds_publisher --example hello_dds_subscriber
# Terminal 1
./target/debug/examples/hello_dds_subscriber
# Terminal 2
./target/debug/examples/hello_dds_publisher

Use the corresponding .exe paths on Windows. The maintained publisher and subscriber use domain 0 and topic Chatter. They demonstrate opaque RawBytes payloads, not generated-type or cross-vendor conformance. Confirm matching output in the subscriber. Both run until interrupted.

See setup and configuration and the complete walkthrough. For generated types, see zerodds-build.

Source map

The workspace manifest identifies current crates and versions. Do not infer the current architecture from old crate counts.

  • DCPS: participants, topics, readers and writers.
  • IDL compiler and build integration: the current generation entrypoints.
  • Configuration loader: base files, sorted drop-ins, explicit includes and provenance. Runtime selection is a separate consumer contract described in the getting-started guide.
  • Architecture documentation: design references whose dates and source links must be considered alongside the current manifest.

Language entrypoints

These links identify implementations in the checkout, not availability of new packages in public registries. Generated codecs and native DDS endpoints are distinct layers.

Language Current source entrypoint
Rust zerodds-dcps, Rust facade
C C API
C++ C++ binding
C# Native binding, with separate CDR/wire runtime dependencies
Java Native Java DDS PSM, not an assumed JNI implementation
Python PyO3 binding, Python 3.9+, exact zerodds-wire dependency in pyproject.toml
TypeScript / Node koffi-based native binding; generated codecs use the separate @zerodds/wire package
TypeScript / browser Browser binding

The presence of a language entrypoint does not establish equal API coverage, transport support or wire representations across all bindings. Follow its current source and measured examples.

Packaging and deployment

Packaging sources describe platform-specific build inputs. Their presence does not mean that every package repository, installer, architecture or container image is available or verified for RC7.

Start with the scoped source build above. Full-workspace builds include optional bridges, native bindings and system-library integrations and require their platform dependencies. For example, the durability lakehouse adapter requires libduckdb. Do not assume every other crate is dependency-free.

The toolchain file pins Rust 1.97.1. The deployment specification describes configuration and layout contracts, not a release-channel availability check.

Documentation

These links do not collectively approve every historical guide or claim. Release coordination, infrastructure notes and unfinished investigations belong in internal/, separate from product-facing instructions.

Contributing and security

See CONTRIBUTING.md, Code of Conduct and SECURITY.md. Do not post vulnerability details in public issues.

License

Apache License 2.0. See LICENSE and NOTICE.

About

OSS DDS implementation in Rust

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

20 stars

Watchers

3 watching

Forks

Releases

Packages

Used by

Contributors

Languages