Package: libzenohc
Version: 0.7.0-rc
Architecture: arm64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 9165
Depends: libc6:arm64 (>= 2.31)
Filename: 0.7.0-rc/libzenohc_0.7.0-rc_arm64.deb
Size: 2478852
MD5sum: e7db37a94626fad25dd1af443116450b
SHA1: dedcee7ec08021f301d25e05beea6f0864ca0c46
SHA256: 4aebaa093d262174e6c3daac9d56184cf5c83933d8f53844461075bf520bc55c
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: The zenoh C client API
.
[](https://github.com/eclipse-zenoh/zenoh-c/actions?query=workflow%3A%22CI%22)
[](https://zenoh-c.readthedocs.io/en/latest/?badge=latest)
[](https://github.com/eclipse-zenoh/roadmap/discussions)
[](https://discord.gg/2GJ958VuHs)
[](https://choosealicense.com/licenses/epl-2.0/)
[](https://opensource.org/licenses/Apache-2.0)
.
.
# Eclipse Zenoh
.
The Eclipse Zenoh: Zero Overhead Pub/sub, Store/Query and Compute.
.
Zenoh (pronounce _/zeno/_) unifies data in motion, data at rest and
computations. It carefully blends traditional pub/sub with geo-distributed
storages, queries and computations, while retaining a level of time and space
efficiency that is well beyond any of the mainstream stacks.
.
Check the website [zenoh.io](http://zenoh.io) and the
[roadmap](https://github.com/eclipse-zenoh/roadmap) for more detailed
information.
.
-------------------------------
# C API
.
This repository provides a C binding based on the main [Zenoh implementation
written in Rust](https://github.com/eclipse-zenoh/zenoh).
.
-------------------------------
## How to build it
.
> :warning: **WARNING** :warning: : Zenoh and its ecosystem are under active
development. When you build from git, make sure you also build from git any
other Zenoh repository you plan to use (e.g. binding, plugin, backend, etc.).
It may happen that some changes in git are not compatible with the most recent
packaged Zenoh release (e.g. deb, docker, pip). We put particular effort in
mantaining compatibility between the various git repositories in the Zenoh
project.
.
1. Make sure that [rust](https://www.rust-lang.org) is available on your
platform:
.
-- Ubuntu --
.
```bash
$ sudo apt-get install rustc
```
.
-- MacOS --
.
```bash
$ brew install rust
```
.
2. Clone the [source] with `git`:
.
```sh
git clone https://github.com/eclipse-zenoh/zenoh-c.git
cd zenoh-c
```
.
[source]: https://github.com/eclipse-zenoh/zenoh-c
.
3. Build and install:
.
```bash
$ cd /path/to/zenoh-c
$ mkdir -p build && cd build
$ cmake -DCMAKE_BUILD_TYPE=Release ..
$ cmake --build .
$ cmake --build . --target install # on linux use **sudo**
```
.
You may alternatively use `-DCMAKE_BUILD_TYPE=RelWithDebInfo` if you wish to
keep the debug symbols.
.
Note that the `install` target is only available for `Release` and
`RelWithDebInfo` builds.
CMake also offers the `Debug` build type, which we do not allow as an `install`
target since you may suffer a significant performance hit if accidentally using
this one.
Finally, CMake typicall offers a `MinSizeRel` build type. While we do not
prevent you from using it, note that it is strictly equivalent to running a
`Release` build.
.
## Building the Examples
.
```bash
$ cd /path/to/zenoh-c
$ mkdir -p build && cd build #
$ cmake -DCMAKE_BUILD_TYPE=Release .. # If Ninja is installed on your system,
adding `-GNinja` to this command can greatly speed up the build time
$ cmake --build . --target examples
```
.
You may also use `--target ` if you wish to only build a specific
example.
.
All build artifacts will be in the `/path/to/zenoh-c/target/release` directory.
.
## Running the Examples
.
### Basic Pub/Sub Example
```bash
$ ./target/release/examples/z_sub
```
.
```bash
$ ./target/release/examples/z_pub
```
.
### Queryable and Query Example
```bash
$ ./target/release/examples/z_queryable
```
.
```bash
$ ./target/release/examples/z_get
```
.
## Running the Throughput Examples
```bash
$ ./target/release/examples/z_sub_thgr
```
.
```bash
$ ./target/release/examples/z_pub_thgr
```
.
## API conventions
Many of the types exposed by the `zenoh-c` API are types for which destruction
is necessary. To help you spot these types, we named them with the convention
that any destructible type must start by `z_owned`.
.
For maximum performance, we try to make as few copies as possible. Sometimes,
this implies moving data that you `z_owned`. Any function that takes a
non-const pointer to a `z_owned` type will perform its destruction. To make
this pattern more obvious, we encourage you to use the `z_move` macro instead
of a simple `&` to create these pointers. Rest assured that all `z_owned` types
are double-free safe, and that you may check whether any `z_owned_X_t` typed
value is still valid by using `z_X_check(&val)`, or the `z_check(val)` macro if
you're using C11.
.
We hope this convention will help you streamline your memory-safe usage of
zenoh, as following it should make looking for leaks trivial: simply search for
paths where a value of a `z_owned` type hasn't been passed to a function using
`z_move`.
.
Functions that simply need to borrow your data will instead take values of the
associated `z_X_t` type. You may construct them using `z_X_loan(&val)` (or the
`z_loan(val)` generic macro with C11).
.
Note that some `z_X_t` typed values can be constructed without needing to
`z_borrow` their owned variants. This allows you to reduce the amount of copies
realized in your program.
.
The examples have been written with C11 in mind, using the conventions we
encourage you to follow.
.
Finally, we strongly advise that you refrain from using structure field that
starts with `_`:
* We try to maintain a common API between `zenoh-c` and
[`zenoh-pico`](https://github.com/eclipse-zenoh/zenoh-pico), such that porting
code from one to the other is, ideally, trivial. However, some types must have
distinct representations in either library, meaning that using these
representations explicitly will get you in trouble when porting.
* We reserve the right to change the memory layout of any type which has
`_`-prefixed fields, so trying to use them might cause your code to break on
updates.
.
## Logging
By default, zenoh-c enables Zenoh's logging library upon using the `z_open` or
`z_scout` functions. This behaviour can be disabled by adding
`-DDISABLE_LOGGER_AUTOINIT:bool=true` to the `cmake` configuration command. The
logger may then be manually re-enabled with the `zc_init_logger` function.
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-c
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-c
Package: libzenohc
Version: 0.7.0-rc
Architecture: armhf
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 9315
Depends: libc6:armhf (>= 2.31)
Filename: 0.7.0-rc/libzenohc_0.7.0-rc_armhf.deb
Size: 2555404
MD5sum: ef1723ba19b242fcedfd2659439dd1b7
SHA1: b46da96738969abef97df74066de2f98b71dca34
SHA256: 54d7621b5b86170f87e4f817c83c3bfa23c6a128154d5c74bda5602455d2181d
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: The zenoh C client API
.
[](https://github.com/eclipse-zenoh/zenoh-c/actions?query=workflow%3A%22CI%22)
[](https://zenoh-c.readthedocs.io/en/latest/?badge=latest)
[](https://github.com/eclipse-zenoh/roadmap/discussions)
[](https://discord.gg/2GJ958VuHs)
[](https://choosealicense.com/licenses/epl-2.0/)
[](https://opensource.org/licenses/Apache-2.0)
.
.
# Eclipse Zenoh
.
The Eclipse Zenoh: Zero Overhead Pub/sub, Store/Query and Compute.
.
Zenoh (pronounce _/zeno/_) unifies data in motion, data at rest and
computations. It carefully blends traditional pub/sub with geo-distributed
storages, queries and computations, while retaining a level of time and space
efficiency that is well beyond any of the mainstream stacks.
.
Check the website [zenoh.io](http://zenoh.io) and the
[roadmap](https://github.com/eclipse-zenoh/roadmap) for more detailed
information.
.
-------------------------------
# C API
.
This repository provides a C binding based on the main [Zenoh implementation
written in Rust](https://github.com/eclipse-zenoh/zenoh).
.
-------------------------------
## How to build it
.
> :warning: **WARNING** :warning: : Zenoh and its ecosystem are under active
development. When you build from git, make sure you also build from git any
other Zenoh repository you plan to use (e.g. binding, plugin, backend, etc.).
It may happen that some changes in git are not compatible with the most recent
packaged Zenoh release (e.g. deb, docker, pip). We put particular effort in
mantaining compatibility between the various git repositories in the Zenoh
project.
.
1. Make sure that [rust](https://www.rust-lang.org) is available on your
platform:
.
-- Ubuntu --
.
```bash
$ sudo apt-get install rustc
```
.
-- MacOS --
.
```bash
$ brew install rust
```
.
2. Clone the [source] with `git`:
.
```sh
git clone https://github.com/eclipse-zenoh/zenoh-c.git
cd zenoh-c
```
.
[source]: https://github.com/eclipse-zenoh/zenoh-c
.
3. Build and install:
.
```bash
$ cd /path/to/zenoh-c
$ mkdir -p build && cd build
$ cmake -DCMAKE_BUILD_TYPE=Release ..
$ cmake --build .
$ cmake --build . --target install # on linux use **sudo**
```
.
You may alternatively use `-DCMAKE_BUILD_TYPE=RelWithDebInfo` if you wish to
keep the debug symbols.
.
Note that the `install` target is only available for `Release` and
`RelWithDebInfo` builds.
CMake also offers the `Debug` build type, which we do not allow as an `install`
target since you may suffer a significant performance hit if accidentally using
this one.
Finally, CMake typicall offers a `MinSizeRel` build type. While we do not
prevent you from using it, note that it is strictly equivalent to running a
`Release` build.
.
## Building the Examples
.
```bash
$ cd /path/to/zenoh-c
$ mkdir -p build && cd build #
$ cmake -DCMAKE_BUILD_TYPE=Release .. # If Ninja is installed on your system,
adding `-GNinja` to this command can greatly speed up the build time
$ cmake --build . --target examples
```
.
You may also use `--target ` if you wish to only build a specific
example.
.
All build artifacts will be in the `/path/to/zenoh-c/target/release` directory.
.
## Running the Examples
.
### Basic Pub/Sub Example
```bash
$ ./target/release/examples/z_sub
```
.
```bash
$ ./target/release/examples/z_pub
```
.
### Queryable and Query Example
```bash
$ ./target/release/examples/z_queryable
```
.
```bash
$ ./target/release/examples/z_get
```
.
## Running the Throughput Examples
```bash
$ ./target/release/examples/z_sub_thgr
```
.
```bash
$ ./target/release/examples/z_pub_thgr
```
.
## API conventions
Many of the types exposed by the `zenoh-c` API are types for which destruction
is necessary. To help you spot these types, we named them with the convention
that any destructible type must start by `z_owned`.
.
For maximum performance, we try to make as few copies as possible. Sometimes,
this implies moving data that you `z_owned`. Any function that takes a
non-const pointer to a `z_owned` type will perform its destruction. To make
this pattern more obvious, we encourage you to use the `z_move` macro instead
of a simple `&` to create these pointers. Rest assured that all `z_owned` types
are double-free safe, and that you may check whether any `z_owned_X_t` typed
value is still valid by using `z_X_check(&val)`, or the `z_check(val)` macro if
you're using C11.
.
We hope this convention will help you streamline your memory-safe usage of
zenoh, as following it should make looking for leaks trivial: simply search for
paths where a value of a `z_owned` type hasn't been passed to a function using
`z_move`.
.
Functions that simply need to borrow your data will instead take values of the
associated `z_X_t` type. You may construct them using `z_X_loan(&val)` (or the
`z_loan(val)` generic macro with C11).
.
Note that some `z_X_t` typed values can be constructed without needing to
`z_borrow` their owned variants. This allows you to reduce the amount of copies
realized in your program.
.
The examples have been written with C11 in mind, using the conventions we
encourage you to follow.
.
Finally, we strongly advise that you refrain from using structure field that
starts with `_`:
* We try to maintain a common API between `zenoh-c` and
[`zenoh-pico`](https://github.com/eclipse-zenoh/zenoh-pico), such that porting
code from one to the other is, ideally, trivial. However, some types must have
distinct representations in either library, meaning that using these
representations explicitly will get you in trouble when porting.
* We reserve the right to change the memory layout of any type which has
`_`-prefixed fields, so trying to use them might cause your code to break on
updates.
.
## Logging
By default, zenoh-c enables Zenoh's logging library upon using the `z_open` or
`z_scout` functions. This behaviour can be disabled by adding
`-DDISABLE_LOGGER_AUTOINIT:bool=true` to the `cmake` configuration command. The
logger may then be manually re-enabled with the `zc_init_logger` function.
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-c
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-c
Package: libzenohc
Version: 0.7.0-rc
Architecture: armel
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 9448
Depends: libc6:armel (>= 2.31)
Filename: 0.7.0-rc/libzenohc_0.7.0-rc_armel.deb
Size: 2549204
MD5sum: d78e51884c451a98796e8eed8003773f
SHA1: a1cdbe598cf8335201f87efefe2314c3399113b5
SHA256: 3c48371cef7bff219b7f39e992fa4e2e80a353a332cf4afae974723347526a27
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: The zenoh C client API
.
[](https://github.com/eclipse-zenoh/zenoh-c/actions?query=workflow%3A%22CI%22)
[](https://zenoh-c.readthedocs.io/en/latest/?badge=latest)
[](https://github.com/eclipse-zenoh/roadmap/discussions)
[](https://discord.gg/2GJ958VuHs)
[](https://choosealicense.com/licenses/epl-2.0/)
[](https://opensource.org/licenses/Apache-2.0)
.
.
# Eclipse Zenoh
.
The Eclipse Zenoh: Zero Overhead Pub/sub, Store/Query and Compute.
.
Zenoh (pronounce _/zeno/_) unifies data in motion, data at rest and
computations. It carefully blends traditional pub/sub with geo-distributed
storages, queries and computations, while retaining a level of time and space
efficiency that is well beyond any of the mainstream stacks.
.
Check the website [zenoh.io](http://zenoh.io) and the
[roadmap](https://github.com/eclipse-zenoh/roadmap) for more detailed
information.
.
-------------------------------
# C API
.
This repository provides a C binding based on the main [Zenoh implementation
written in Rust](https://github.com/eclipse-zenoh/zenoh).
.
-------------------------------
## How to build it
.
> :warning: **WARNING** :warning: : Zenoh and its ecosystem are under active
development. When you build from git, make sure you also build from git any
other Zenoh repository you plan to use (e.g. binding, plugin, backend, etc.).
It may happen that some changes in git are not compatible with the most recent
packaged Zenoh release (e.g. deb, docker, pip). We put particular effort in
mantaining compatibility between the various git repositories in the Zenoh
project.
.
1. Make sure that [rust](https://www.rust-lang.org) is available on your
platform:
.
-- Ubuntu --
.
```bash
$ sudo apt-get install rustc
```
.
-- MacOS --
.
```bash
$ brew install rust
```
.
2. Clone the [source] with `git`:
.
```sh
git clone https://github.com/eclipse-zenoh/zenoh-c.git
cd zenoh-c
```
.
[source]: https://github.com/eclipse-zenoh/zenoh-c
.
3. Build and install:
.
```bash
$ cd /path/to/zenoh-c
$ mkdir -p build && cd build
$ cmake -DCMAKE_BUILD_TYPE=Release ..
$ cmake --build .
$ cmake --build . --target install # on linux use **sudo**
```
.
You may alternatively use `-DCMAKE_BUILD_TYPE=RelWithDebInfo` if you wish to
keep the debug symbols.
.
Note that the `install` target is only available for `Release` and
`RelWithDebInfo` builds.
CMake also offers the `Debug` build type, which we do not allow as an `install`
target since you may suffer a significant performance hit if accidentally using
this one.
Finally, CMake typicall offers a `MinSizeRel` build type. While we do not
prevent you from using it, note that it is strictly equivalent to running a
`Release` build.
.
## Building the Examples
.
```bash
$ cd /path/to/zenoh-c
$ mkdir -p build && cd build #
$ cmake -DCMAKE_BUILD_TYPE=Release .. # If Ninja is installed on your system,
adding `-GNinja` to this command can greatly speed up the build time
$ cmake --build . --target examples
```
.
You may also use `--target ` if you wish to only build a specific
example.
.
All build artifacts will be in the `/path/to/zenoh-c/target/release` directory.
.
## Running the Examples
.
### Basic Pub/Sub Example
```bash
$ ./target/release/examples/z_sub
```
.
```bash
$ ./target/release/examples/z_pub
```
.
### Queryable and Query Example
```bash
$ ./target/release/examples/z_queryable
```
.
```bash
$ ./target/release/examples/z_get
```
.
## Running the Throughput Examples
```bash
$ ./target/release/examples/z_sub_thgr
```
.
```bash
$ ./target/release/examples/z_pub_thgr
```
.
## API conventions
Many of the types exposed by the `zenoh-c` API are types for which destruction
is necessary. To help you spot these types, we named them with the convention
that any destructible type must start by `z_owned`.
.
For maximum performance, we try to make as few copies as possible. Sometimes,
this implies moving data that you `z_owned`. Any function that takes a
non-const pointer to a `z_owned` type will perform its destruction. To make
this pattern more obvious, we encourage you to use the `z_move` macro instead
of a simple `&` to create these pointers. Rest assured that all `z_owned` types
are double-free safe, and that you may check whether any `z_owned_X_t` typed
value is still valid by using `z_X_check(&val)`, or the `z_check(val)` macro if
you're using C11.
.
We hope this convention will help you streamline your memory-safe usage of
zenoh, as following it should make looking for leaks trivial: simply search for
paths where a value of a `z_owned` type hasn't been passed to a function using
`z_move`.
.
Functions that simply need to borrow your data will instead take values of the
associated `z_X_t` type. You may construct them using `z_X_loan(&val)` (or the
`z_loan(val)` generic macro with C11).
.
Note that some `z_X_t` typed values can be constructed without needing to
`z_borrow` their owned variants. This allows you to reduce the amount of copies
realized in your program.
.
The examples have been written with C11 in mind, using the conventions we
encourage you to follow.
.
Finally, we strongly advise that you refrain from using structure field that
starts with `_`:
* We try to maintain a common API between `zenoh-c` and
[`zenoh-pico`](https://github.com/eclipse-zenoh/zenoh-pico), such that porting
code from one to the other is, ideally, trivial. However, some types must have
distinct representations in either library, meaning that using these
representations explicitly will get you in trouble when porting.
* We reserve the right to change the memory layout of any type which has
`_`-prefixed fields, so trying to use them might cause your code to break on
updates.
.
## Logging
By default, zenoh-c enables Zenoh's logging library upon using the `z_open` or
`z_scout` functions. This behaviour can be disabled by adding
`-DDISABLE_LOGGER_AUTOINIT:bool=true` to the `cmake` configuration command. The
logger may then be manually re-enabled with the `zc_init_logger` function.
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-c
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-c
Package: libzenohc
Version: 0.7.0-rc
Architecture: amd64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 10357
Depends: libc6 (>= 2.28)
Filename: 0.7.0-rc/libzenohc_0.7.0-rc_amd64.deb
Size: 2802116
MD5sum: 93ed00bdbee4e0651bc5878f477830a3
SHA1: 36184a4a37230cf1b4c02d0306230679cf302c22
SHA256: 14615f2ddfed9d31d6b16b3c1f6728c4f0d479600932bb54237effefed18d09c
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: The zenoh C client API
.
[](https://github.com/eclipse-zenoh/zenoh-c/actions?query=workflow%3A%22CI%22)
[](https://zenoh-c.readthedocs.io/en/latest/?badge=latest)
[](https://github.com/eclipse-zenoh/roadmap/discussions)
[](https://discord.gg/2GJ958VuHs)
[](https://choosealicense.com/licenses/epl-2.0/)
[](https://opensource.org/licenses/Apache-2.0)
.
.
# Eclipse Zenoh
.
The Eclipse Zenoh: Zero Overhead Pub/sub, Store/Query and Compute.
.
Zenoh (pronounce _/zeno/_) unifies data in motion, data at rest and
computations. It carefully blends traditional pub/sub with geo-distributed
storages, queries and computations, while retaining a level of time and space
efficiency that is well beyond any of the mainstream stacks.
.
Check the website [zenoh.io](http://zenoh.io) and the
[roadmap](https://github.com/eclipse-zenoh/roadmap) for more detailed
information.
.
-------------------------------
# C API
.
This repository provides a C binding based on the main [Zenoh implementation
written in Rust](https://github.com/eclipse-zenoh/zenoh).
.
-------------------------------
## How to build it
.
> :warning: **WARNING** :warning: : Zenoh and its ecosystem are under active
development. When you build from git, make sure you also build from git any
other Zenoh repository you plan to use (e.g. binding, plugin, backend, etc.).
It may happen that some changes in git are not compatible with the most recent
packaged Zenoh release (e.g. deb, docker, pip). We put particular effort in
mantaining compatibility between the various git repositories in the Zenoh
project.
.
1. Make sure that [rust](https://www.rust-lang.org) is available on your
platform:
.
-- Ubuntu --
.
```bash
$ sudo apt-get install rustc
```
.
-- MacOS --
.
```bash
$ brew install rust
```
.
2. Clone the [source] with `git`:
.
```sh
git clone https://github.com/eclipse-zenoh/zenoh-c.git
cd zenoh-c
```
.
[source]: https://github.com/eclipse-zenoh/zenoh-c
.
3. Build and install:
.
```bash
$ cd /path/to/zenoh-c
$ mkdir -p build && cd build
$ cmake -DCMAKE_BUILD_TYPE=Release ..
$ cmake --build .
$ cmake --build . --target install # on linux use **sudo**
```
.
You may alternatively use `-DCMAKE_BUILD_TYPE=RelWithDebInfo` if you wish to
keep the debug symbols.
.
Note that the `install` target is only available for `Release` and
`RelWithDebInfo` builds.
CMake also offers the `Debug` build type, which we do not allow as an `install`
target since you may suffer a significant performance hit if accidentally using
this one.
Finally, CMake typicall offers a `MinSizeRel` build type. While we do not
prevent you from using it, note that it is strictly equivalent to running a
`Release` build.
.
## Building the Examples
.
```bash
$ cd /path/to/zenoh-c
$ mkdir -p build && cd build #
$ cmake -DCMAKE_BUILD_TYPE=Release .. # If Ninja is installed on your system,
adding `-GNinja` to this command can greatly speed up the build time
$ cmake --build . --target examples
```
.
You may also use `--target ` if you wish to only build a specific
example.
.
All build artifacts will be in the `/path/to/zenoh-c/target/release` directory.
.
## Running the Examples
.
### Basic Pub/Sub Example
```bash
$ ./target/release/examples/z_sub
```
.
```bash
$ ./target/release/examples/z_pub
```
.
### Queryable and Query Example
```bash
$ ./target/release/examples/z_queryable
```
.
```bash
$ ./target/release/examples/z_get
```
.
## Running the Throughput Examples
```bash
$ ./target/release/examples/z_sub_thgr
```
.
```bash
$ ./target/release/examples/z_pub_thgr
```
.
## API conventions
Many of the types exposed by the `zenoh-c` API are types for which destruction
is necessary. To help you spot these types, we named them with the convention
that any destructible type must start by `z_owned`.
.
For maximum performance, we try to make as few copies as possible. Sometimes,
this implies moving data that you `z_owned`. Any function that takes a
non-const pointer to a `z_owned` type will perform its destruction. To make
this pattern more obvious, we encourage you to use the `z_move` macro instead
of a simple `&` to create these pointers. Rest assured that all `z_owned` types
are double-free safe, and that you may check whether any `z_owned_X_t` typed
value is still valid by using `z_X_check(&val)`, or the `z_check(val)` macro if
you're using C11.
.
We hope this convention will help you streamline your memory-safe usage of
zenoh, as following it should make looking for leaks trivial: simply search for
paths where a value of a `z_owned` type hasn't been passed to a function using
`z_move`.
.
Functions that simply need to borrow your data will instead take values of the
associated `z_X_t` type. You may construct them using `z_X_loan(&val)` (or the
`z_loan(val)` generic macro with C11).
.
Note that some `z_X_t` typed values can be constructed without needing to
`z_borrow` their owned variants. This allows you to reduce the amount of copies
realized in your program.
.
The examples have been written with C11 in mind, using the conventions we
encourage you to follow.
.
Finally, we strongly advise that you refrain from using structure field that
starts with `_`:
* We try to maintain a common API between `zenoh-c` and
[`zenoh-pico`](https://github.com/eclipse-zenoh/zenoh-pico), such that porting
code from one to the other is, ideally, trivial. However, some types must have
distinct representations in either library, meaning that using these
representations explicitly will get you in trouble when porting.
* We reserve the right to change the memory layout of any type which has
`_`-prefixed fields, so trying to use them might cause your code to break on
updates.
.
## Logging
By default, zenoh-c enables Zenoh's logging library upon using the `z_open` or
`z_scout` functions. This behaviour can be disabled by adding
`-DDISABLE_LOGGER_AUTOINIT:bool=true` to the `cmake` configuration command. The
logger may then be manually re-enabled with the `zc_init_logger` function.
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-c
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-c
Package: libzenohc-dev
Version: 0.7.0-rc
Architecture: armel
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 115
Depends: libzenohc (=0.7.0-rc)
Filename: 0.7.0-rc/libzenohc-dev_0.7.0-rc_armel.deb
Size: 23216
MD5sum: 58a6e9abe9c3701eaeaa68be4cf8e147
SHA1: 7192dc0b82c5c76beb5743e4e63f566fcf6df4cc
SHA256: 0d659a470110147ef8dc6a441375ecdb07b8ab9e06414104c74063ce66ae271e
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: The zenoh C client API
.
[](https://github.com/eclipse-zenoh/zenoh-c/actions?query=workflow%3A%22CI%22)
[](https://zenoh-c.readthedocs.io/en/latest/?badge=latest)
[](https://github.com/eclipse-zenoh/roadmap/discussions)
[](https://discord.gg/2GJ958VuHs)
[](https://choosealicense.com/licenses/epl-2.0/)
[](https://opensource.org/licenses/Apache-2.0)
.
.
# Eclipse Zenoh
.
The Eclipse Zenoh: Zero Overhead Pub/sub, Store/Query and Compute.
.
Zenoh (pronounce _/zeno/_) unifies data in motion, data at rest and
computations. It carefully blends traditional pub/sub with geo-distributed
storages, queries and computations, while retaining a level of time and space
efficiency that is well beyond any of the mainstream stacks.
.
Check the website [zenoh.io](http://zenoh.io) and the
[roadmap](https://github.com/eclipse-zenoh/roadmap) for more detailed
information.
.
-------------------------------
# C API
.
This repository provides a C binding based on the main [Zenoh implementation
written in Rust](https://github.com/eclipse-zenoh/zenoh).
.
-------------------------------
## How to build it
.
> :warning: **WARNING** :warning: : Zenoh and its ecosystem are under active
development. When you build from git, make sure you also build from git any
other Zenoh repository you plan to use (e.g. binding, plugin, backend, etc.).
It may happen that some changes in git are not compatible with the most recent
packaged Zenoh release (e.g. deb, docker, pip). We put particular effort in
mantaining compatibility between the various git repositories in the Zenoh
project.
.
1. Make sure that [rust](https://www.rust-lang.org) is available on your
platform:
.
-- Ubuntu --
.
```bash
$ sudo apt-get install rustc
```
.
-- MacOS --
.
```bash
$ brew install rust
```
.
2. Clone the [source] with `git`:
.
```sh
git clone https://github.com/eclipse-zenoh/zenoh-c.git
cd zenoh-c
```
.
[source]: https://github.com/eclipse-zenoh/zenoh-c
.
3. Build and install:
.
```bash
$ cd /path/to/zenoh-c
$ mkdir -p build && cd build
$ cmake -DCMAKE_BUILD_TYPE=Release ..
$ cmake --build .
$ cmake --build . --target install # on linux use **sudo**
```
.
You may alternatively use `-DCMAKE_BUILD_TYPE=RelWithDebInfo` if you wish to
keep the debug symbols.
.
Note that the `install` target is only available for `Release` and
`RelWithDebInfo` builds.
CMake also offers the `Debug` build type, which we do not allow as an `install`
target since you may suffer a significant performance hit if accidentally using
this one.
Finally, CMake typicall offers a `MinSizeRel` build type. While we do not
prevent you from using it, note that it is strictly equivalent to running a
`Release` build.
.
## Building the Examples
.
```bash
$ cd /path/to/zenoh-c
$ mkdir -p build && cd build #
$ cmake -DCMAKE_BUILD_TYPE=Release .. # If Ninja is installed on your system,
adding `-GNinja` to this command can greatly speed up the build time
$ cmake --build . --target examples
```
.
You may also use `--target ` if you wish to only build a specific
example.
.
All build artifacts will be in the `/path/to/zenoh-c/target/release` directory.
.
## Running the Examples
.
### Basic Pub/Sub Example
```bash
$ ./target/release/examples/z_sub
```
.
```bash
$ ./target/release/examples/z_pub
```
.
### Queryable and Query Example
```bash
$ ./target/release/examples/z_queryable
```
.
```bash
$ ./target/release/examples/z_get
```
.
## Running the Throughput Examples
```bash
$ ./target/release/examples/z_sub_thgr
```
.
```bash
$ ./target/release/examples/z_pub_thgr
```
.
## API conventions
Many of the types exposed by the `zenoh-c` API are types for which destruction
is necessary. To help you spot these types, we named them with the convention
that any destructible type must start by `z_owned`.
.
For maximum performance, we try to make as few copies as possible. Sometimes,
this implies moving data that you `z_owned`. Any function that takes a
non-const pointer to a `z_owned` type will perform its destruction. To make
this pattern more obvious, we encourage you to use the `z_move` macro instead
of a simple `&` to create these pointers. Rest assured that all `z_owned` types
are double-free safe, and that you may check whether any `z_owned_X_t` typed
value is still valid by using `z_X_check(&val)`, or the `z_check(val)` macro if
you're using C11.
.
We hope this convention will help you streamline your memory-safe usage of
zenoh, as following it should make looking for leaks trivial: simply search for
paths where a value of a `z_owned` type hasn't been passed to a function using
`z_move`.
.
Functions that simply need to borrow your data will instead take values of the
associated `z_X_t` type. You may construct them using `z_X_loan(&val)` (or the
`z_loan(val)` generic macro with C11).
.
Note that some `z_X_t` typed values can be constructed without needing to
`z_borrow` their owned variants. This allows you to reduce the amount of copies
realized in your program.
.
The examples have been written with C11 in mind, using the conventions we
encourage you to follow.
.
Finally, we strongly advise that you refrain from using structure field that
starts with `_`:
* We try to maintain a common API between `zenoh-c` and
[`zenoh-pico`](https://github.com/eclipse-zenoh/zenoh-pico), such that porting
code from one to the other is, ideally, trivial. However, some types must have
distinct representations in either library, meaning that using these
representations explicitly will get you in trouble when porting.
* We reserve the right to change the memory layout of any type which has
`_`-prefixed fields, so trying to use them might cause your code to break on
updates.
.
## Logging
By default, zenoh-c enables Zenoh's logging library upon using the `z_open` or
`z_scout` functions. This behaviour can be disabled by adding
`-DDISABLE_LOGGER_AUTOINIT:bool=true` to the `cmake` configuration command. The
logger may then be manually re-enabled with the `zc_init_logger` function.
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-c
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-c
Package: libzenohc-dev
Version: 0.7.0-rc
Architecture: armhf
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 115
Depends: libzenohc (=0.7.0-rc)
Filename: 0.7.0-rc/libzenohc-dev_0.7.0-rc_armhf.deb
Size: 23216
MD5sum: 785d11a382619baf35be6c5a2f94f6aa
SHA1: 8801ea286f5abf692217644b6f8cdb1b2c65b1d1
SHA256: f895227cb5d6615f5fae65ad9cd115788b7007484061b9e807a3631c1d8e1200
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: The zenoh C client API
.
[](https://github.com/eclipse-zenoh/zenoh-c/actions?query=workflow%3A%22CI%22)
[](https://zenoh-c.readthedocs.io/en/latest/?badge=latest)
[](https://github.com/eclipse-zenoh/roadmap/discussions)
[](https://discord.gg/2GJ958VuHs)
[](https://choosealicense.com/licenses/epl-2.0/)
[](https://opensource.org/licenses/Apache-2.0)
.
.
# Eclipse Zenoh
.
The Eclipse Zenoh: Zero Overhead Pub/sub, Store/Query and Compute.
.
Zenoh (pronounce _/zeno/_) unifies data in motion, data at rest and
computations. It carefully blends traditional pub/sub with geo-distributed
storages, queries and computations, while retaining a level of time and space
efficiency that is well beyond any of the mainstream stacks.
.
Check the website [zenoh.io](http://zenoh.io) and the
[roadmap](https://github.com/eclipse-zenoh/roadmap) for more detailed
information.
.
-------------------------------
# C API
.
This repository provides a C binding based on the main [Zenoh implementation
written in Rust](https://github.com/eclipse-zenoh/zenoh).
.
-------------------------------
## How to build it
.
> :warning: **WARNING** :warning: : Zenoh and its ecosystem are under active
development. When you build from git, make sure you also build from git any
other Zenoh repository you plan to use (e.g. binding, plugin, backend, etc.).
It may happen that some changes in git are not compatible with the most recent
packaged Zenoh release (e.g. deb, docker, pip). We put particular effort in
mantaining compatibility between the various git repositories in the Zenoh
project.
.
1. Make sure that [rust](https://www.rust-lang.org) is available on your
platform:
.
-- Ubuntu --
.
```bash
$ sudo apt-get install rustc
```
.
-- MacOS --
.
```bash
$ brew install rust
```
.
2. Clone the [source] with `git`:
.
```sh
git clone https://github.com/eclipse-zenoh/zenoh-c.git
cd zenoh-c
```
.
[source]: https://github.com/eclipse-zenoh/zenoh-c
.
3. Build and install:
.
```bash
$ cd /path/to/zenoh-c
$ mkdir -p build && cd build
$ cmake -DCMAKE_BUILD_TYPE=Release ..
$ cmake --build .
$ cmake --build . --target install # on linux use **sudo**
```
.
You may alternatively use `-DCMAKE_BUILD_TYPE=RelWithDebInfo` if you wish to
keep the debug symbols.
.
Note that the `install` target is only available for `Release` and
`RelWithDebInfo` builds.
CMake also offers the `Debug` build type, which we do not allow as an `install`
target since you may suffer a significant performance hit if accidentally using
this one.
Finally, CMake typicall offers a `MinSizeRel` build type. While we do not
prevent you from using it, note that it is strictly equivalent to running a
`Release` build.
.
## Building the Examples
.
```bash
$ cd /path/to/zenoh-c
$ mkdir -p build && cd build #
$ cmake -DCMAKE_BUILD_TYPE=Release .. # If Ninja is installed on your system,
adding `-GNinja` to this command can greatly speed up the build time
$ cmake --build . --target examples
```
.
You may also use `--target ` if you wish to only build a specific
example.
.
All build artifacts will be in the `/path/to/zenoh-c/target/release` directory.
.
## Running the Examples
.
### Basic Pub/Sub Example
```bash
$ ./target/release/examples/z_sub
```
.
```bash
$ ./target/release/examples/z_pub
```
.
### Queryable and Query Example
```bash
$ ./target/release/examples/z_queryable
```
.
```bash
$ ./target/release/examples/z_get
```
.
## Running the Throughput Examples
```bash
$ ./target/release/examples/z_sub_thgr
```
.
```bash
$ ./target/release/examples/z_pub_thgr
```
.
## API conventions
Many of the types exposed by the `zenoh-c` API are types for which destruction
is necessary. To help you spot these types, we named them with the convention
that any destructible type must start by `z_owned`.
.
For maximum performance, we try to make as few copies as possible. Sometimes,
this implies moving data that you `z_owned`. Any function that takes a
non-const pointer to a `z_owned` type will perform its destruction. To make
this pattern more obvious, we encourage you to use the `z_move` macro instead
of a simple `&` to create these pointers. Rest assured that all `z_owned` types
are double-free safe, and that you may check whether any `z_owned_X_t` typed
value is still valid by using `z_X_check(&val)`, or the `z_check(val)` macro if
you're using C11.
.
We hope this convention will help you streamline your memory-safe usage of
zenoh, as following it should make looking for leaks trivial: simply search for
paths where a value of a `z_owned` type hasn't been passed to a function using
`z_move`.
.
Functions that simply need to borrow your data will instead take values of the
associated `z_X_t` type. You may construct them using `z_X_loan(&val)` (or the
`z_loan(val)` generic macro with C11).
.
Note that some `z_X_t` typed values can be constructed without needing to
`z_borrow` their owned variants. This allows you to reduce the amount of copies
realized in your program.
.
The examples have been written with C11 in mind, using the conventions we
encourage you to follow.
.
Finally, we strongly advise that you refrain from using structure field that
starts with `_`:
* We try to maintain a common API between `zenoh-c` and
[`zenoh-pico`](https://github.com/eclipse-zenoh/zenoh-pico), such that porting
code from one to the other is, ideally, trivial. However, some types must have
distinct representations in either library, meaning that using these
representations explicitly will get you in trouble when porting.
* We reserve the right to change the memory layout of any type which has
`_`-prefixed fields, so trying to use them might cause your code to break on
updates.
.
## Logging
By default, zenoh-c enables Zenoh's logging library upon using the `z_open` or
`z_scout` functions. This behaviour can be disabled by adding
`-DDISABLE_LOGGER_AUTOINIT:bool=true` to the `cmake` configuration command. The
logger may then be manually re-enabled with the `zc_init_logger` function.
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-c
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-c
Package: libzenohc-dev
Version: 0.7.0-rc
Architecture: arm64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 115
Depends: libzenohc (=0.7.0-rc)
Filename: 0.7.0-rc/libzenohc-dev_0.7.0-rc_arm64.deb
Size: 23216
MD5sum: 2318c5f9ca2891d0fcd01dc2a7f02a96
SHA1: 129056e93f75c2a83edc84cc6e0c62a6fd2b603d
SHA256: cd1ee1a6cf28124cd2ccb7cbad6443f293001870e41e83f0ad7860e38b7ae722
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: The zenoh C client API
.
[](https://github.com/eclipse-zenoh/zenoh-c/actions?query=workflow%3A%22CI%22)
[](https://zenoh-c.readthedocs.io/en/latest/?badge=latest)
[](https://github.com/eclipse-zenoh/roadmap/discussions)
[](https://discord.gg/2GJ958VuHs)
[](https://choosealicense.com/licenses/epl-2.0/)
[](https://opensource.org/licenses/Apache-2.0)
.
.
# Eclipse Zenoh
.
The Eclipse Zenoh: Zero Overhead Pub/sub, Store/Query and Compute.
.
Zenoh (pronounce _/zeno/_) unifies data in motion, data at rest and
computations. It carefully blends traditional pub/sub with geo-distributed
storages, queries and computations, while retaining a level of time and space
efficiency that is well beyond any of the mainstream stacks.
.
Check the website [zenoh.io](http://zenoh.io) and the
[roadmap](https://github.com/eclipse-zenoh/roadmap) for more detailed
information.
.
-------------------------------
# C API
.
This repository provides a C binding based on the main [Zenoh implementation
written in Rust](https://github.com/eclipse-zenoh/zenoh).
.
-------------------------------
## How to build it
.
> :warning: **WARNING** :warning: : Zenoh and its ecosystem are under active
development. When you build from git, make sure you also build from git any
other Zenoh repository you plan to use (e.g. binding, plugin, backend, etc.).
It may happen that some changes in git are not compatible with the most recent
packaged Zenoh release (e.g. deb, docker, pip). We put particular effort in
mantaining compatibility between the various git repositories in the Zenoh
project.
.
1. Make sure that [rust](https://www.rust-lang.org) is available on your
platform:
.
-- Ubuntu --
.
```bash
$ sudo apt-get install rustc
```
.
-- MacOS --
.
```bash
$ brew install rust
```
.
2. Clone the [source] with `git`:
.
```sh
git clone https://github.com/eclipse-zenoh/zenoh-c.git
cd zenoh-c
```
.
[source]: https://github.com/eclipse-zenoh/zenoh-c
.
3. Build and install:
.
```bash
$ cd /path/to/zenoh-c
$ mkdir -p build && cd build
$ cmake -DCMAKE_BUILD_TYPE=Release ..
$ cmake --build .
$ cmake --build . --target install # on linux use **sudo**
```
.
You may alternatively use `-DCMAKE_BUILD_TYPE=RelWithDebInfo` if you wish to
keep the debug symbols.
.
Note that the `install` target is only available for `Release` and
`RelWithDebInfo` builds.
CMake also offers the `Debug` build type, which we do not allow as an `install`
target since you may suffer a significant performance hit if accidentally using
this one.
Finally, CMake typicall offers a `MinSizeRel` build type. While we do not
prevent you from using it, note that it is strictly equivalent to running a
`Release` build.
.
## Building the Examples
.
```bash
$ cd /path/to/zenoh-c
$ mkdir -p build && cd build #
$ cmake -DCMAKE_BUILD_TYPE=Release .. # If Ninja is installed on your system,
adding `-GNinja` to this command can greatly speed up the build time
$ cmake --build . --target examples
```
.
You may also use `--target ` if you wish to only build a specific
example.
.
All build artifacts will be in the `/path/to/zenoh-c/target/release` directory.
.
## Running the Examples
.
### Basic Pub/Sub Example
```bash
$ ./target/release/examples/z_sub
```
.
```bash
$ ./target/release/examples/z_pub
```
.
### Queryable and Query Example
```bash
$ ./target/release/examples/z_queryable
```
.
```bash
$ ./target/release/examples/z_get
```
.
## Running the Throughput Examples
```bash
$ ./target/release/examples/z_sub_thgr
```
.
```bash
$ ./target/release/examples/z_pub_thgr
```
.
## API conventions
Many of the types exposed by the `zenoh-c` API are types for which destruction
is necessary. To help you spot these types, we named them with the convention
that any destructible type must start by `z_owned`.
.
For maximum performance, we try to make as few copies as possible. Sometimes,
this implies moving data that you `z_owned`. Any function that takes a
non-const pointer to a `z_owned` type will perform its destruction. To make
this pattern more obvious, we encourage you to use the `z_move` macro instead
of a simple `&` to create these pointers. Rest assured that all `z_owned` types
are double-free safe, and that you may check whether any `z_owned_X_t` typed
value is still valid by using `z_X_check(&val)`, or the `z_check(val)` macro if
you're using C11.
.
We hope this convention will help you streamline your memory-safe usage of
zenoh, as following it should make looking for leaks trivial: simply search for
paths where a value of a `z_owned` type hasn't been passed to a function using
`z_move`.
.
Functions that simply need to borrow your data will instead take values of the
associated `z_X_t` type. You may construct them using `z_X_loan(&val)` (or the
`z_loan(val)` generic macro with C11).
.
Note that some `z_X_t` typed values can be constructed without needing to
`z_borrow` their owned variants. This allows you to reduce the amount of copies
realized in your program.
.
The examples have been written with C11 in mind, using the conventions we
encourage you to follow.
.
Finally, we strongly advise that you refrain from using structure field that
starts with `_`:
* We try to maintain a common API between `zenoh-c` and
[`zenoh-pico`](https://github.com/eclipse-zenoh/zenoh-pico), such that porting
code from one to the other is, ideally, trivial. However, some types must have
distinct representations in either library, meaning that using these
representations explicitly will get you in trouble when porting.
* We reserve the right to change the memory layout of any type which has
`_`-prefixed fields, so trying to use them might cause your code to break on
updates.
.
## Logging
By default, zenoh-c enables Zenoh's logging library upon using the `z_open` or
`z_scout` functions. This behaviour can be disabled by adding
`-DDISABLE_LOGGER_AUTOINIT:bool=true` to the `cmake` configuration command. The
logger may then be manually re-enabled with the `zc_init_logger` function.
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-c
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-c
Package: libzenohc-dev
Version: 0.7.0-rc
Architecture: amd64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 115
Depends: libzenohc (=0.7.0-rc)
Filename: 0.7.0-rc/libzenohc-dev_0.7.0-rc_amd64.deb
Size: 23220
MD5sum: b3a87c213db4effe0e33612b3b3a940d
SHA1: 95082e7a5de326659db2d58126269b04ac186b7b
SHA256: 508c3d7d0f7fd050b9609589718a2ce7e7741fbea6cbe93390a2b31f173872dc
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: The zenoh C client API
.
[](https://github.com/eclipse-zenoh/zenoh-c/actions?query=workflow%3A%22CI%22)
[](https://zenoh-c.readthedocs.io/en/latest/?badge=latest)
[](https://github.com/eclipse-zenoh/roadmap/discussions)
[](https://discord.gg/2GJ958VuHs)
[](https://choosealicense.com/licenses/epl-2.0/)
[](https://opensource.org/licenses/Apache-2.0)
.
.
# Eclipse Zenoh
.
The Eclipse Zenoh: Zero Overhead Pub/sub, Store/Query and Compute.
.
Zenoh (pronounce _/zeno/_) unifies data in motion, data at rest and
computations. It carefully blends traditional pub/sub with geo-distributed
storages, queries and computations, while retaining a level of time and space
efficiency that is well beyond any of the mainstream stacks.
.
Check the website [zenoh.io](http://zenoh.io) and the
[roadmap](https://github.com/eclipse-zenoh/roadmap) for more detailed
information.
.
-------------------------------
# C API
.
This repository provides a C binding based on the main [Zenoh implementation
written in Rust](https://github.com/eclipse-zenoh/zenoh).
.
-------------------------------
## How to build it
.
> :warning: **WARNING** :warning: : Zenoh and its ecosystem are under active
development. When you build from git, make sure you also build from git any
other Zenoh repository you plan to use (e.g. binding, plugin, backend, etc.).
It may happen that some changes in git are not compatible with the most recent
packaged Zenoh release (e.g. deb, docker, pip). We put particular effort in
mantaining compatibility between the various git repositories in the Zenoh
project.
.
1. Make sure that [rust](https://www.rust-lang.org) is available on your
platform:
.
-- Ubuntu --
.
```bash
$ sudo apt-get install rustc
```
.
-- MacOS --
.
```bash
$ brew install rust
```
.
2. Clone the [source] with `git`:
.
```sh
git clone https://github.com/eclipse-zenoh/zenoh-c.git
cd zenoh-c
```
.
[source]: https://github.com/eclipse-zenoh/zenoh-c
.
3. Build and install:
.
```bash
$ cd /path/to/zenoh-c
$ mkdir -p build && cd build
$ cmake -DCMAKE_BUILD_TYPE=Release ..
$ cmake --build .
$ cmake --build . --target install # on linux use **sudo**
```
.
You may alternatively use `-DCMAKE_BUILD_TYPE=RelWithDebInfo` if you wish to
keep the debug symbols.
.
Note that the `install` target is only available for `Release` and
`RelWithDebInfo` builds.
CMake also offers the `Debug` build type, which we do not allow as an `install`
target since you may suffer a significant performance hit if accidentally using
this one.
Finally, CMake typicall offers a `MinSizeRel` build type. While we do not
prevent you from using it, note that it is strictly equivalent to running a
`Release` build.
.
## Building the Examples
.
```bash
$ cd /path/to/zenoh-c
$ mkdir -p build && cd build #
$ cmake -DCMAKE_BUILD_TYPE=Release .. # If Ninja is installed on your system,
adding `-GNinja` to this command can greatly speed up the build time
$ cmake --build . --target examples
```
.
You may also use `--target ` if you wish to only build a specific
example.
.
All build artifacts will be in the `/path/to/zenoh-c/target/release` directory.
.
## Running the Examples
.
### Basic Pub/Sub Example
```bash
$ ./target/release/examples/z_sub
```
.
```bash
$ ./target/release/examples/z_pub
```
.
### Queryable and Query Example
```bash
$ ./target/release/examples/z_queryable
```
.
```bash
$ ./target/release/examples/z_get
```
.
## Running the Throughput Examples
```bash
$ ./target/release/examples/z_sub_thgr
```
.
```bash
$ ./target/release/examples/z_pub_thgr
```
.
## API conventions
Many of the types exposed by the `zenoh-c` API are types for which destruction
is necessary. To help you spot these types, we named them with the convention
that any destructible type must start by `z_owned`.
.
For maximum performance, we try to make as few copies as possible. Sometimes,
this implies moving data that you `z_owned`. Any function that takes a
non-const pointer to a `z_owned` type will perform its destruction. To make
this pattern more obvious, we encourage you to use the `z_move` macro instead
of a simple `&` to create these pointers. Rest assured that all `z_owned` types
are double-free safe, and that you may check whether any `z_owned_X_t` typed
value is still valid by using `z_X_check(&val)`, or the `z_check(val)` macro if
you're using C11.
.
We hope this convention will help you streamline your memory-safe usage of
zenoh, as following it should make looking for leaks trivial: simply search for
paths where a value of a `z_owned` type hasn't been passed to a function using
`z_move`.
.
Functions that simply need to borrow your data will instead take values of the
associated `z_X_t` type. You may construct them using `z_X_loan(&val)` (or the
`z_loan(val)` generic macro with C11).
.
Note that some `z_X_t` typed values can be constructed without needing to
`z_borrow` their owned variants. This allows you to reduce the amount of copies
realized in your program.
.
The examples have been written with C11 in mind, using the conventions we
encourage you to follow.
.
Finally, we strongly advise that you refrain from using structure field that
starts with `_`:
* We try to maintain a common API between `zenoh-c` and
[`zenoh-pico`](https://github.com/eclipse-zenoh/zenoh-pico), such that porting
code from one to the other is, ideally, trivial. However, some types must have
distinct representations in either library, meaning that using these
representations explicitly will get you in trouble when porting.
* We reserve the right to change the memory layout of any type which has
`_`-prefixed fields, so trying to use them might cause your code to break on
updates.
.
## Logging
By default, zenoh-c enables Zenoh's logging library upon using the `z_open` or
`z_scout` functions. This behaviour can be disabled by adding
`-DDISABLE_LOGGER_AUTOINIT:bool=true` to the `cmake` configuration command. The
logger may then be manually re-enabled with the `zc_init_logger` function.
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-c
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-c
Package: libzenohpico
Version: 0.7.20221221dev
Architecture: mips
Maintainer: ZettaScale Zenoh Team,
Installed-Size: 4
Depends: libc6 (>=2.12)
Filename: 0.7.0-rc/libzenohpico_0.7.20221221dev_mips.deb
Size: 610
MD5sum: 2f18a80bcba3009e57877d07f5e46816
SHA1: e8104bc1825fe951fc3b50478e1ae048ee06eed4
SHA256: 13d8146e66c6dabbe559cc28dcbe569fe905c6be9daf258a6af42189e366fd16
Section: devel
Priority: optional
Description: The C client library for Eclipse zenoh targeting pico devices
Package: libzenohpico
Version: 0.7.20221221dev
Architecture: armhf
Maintainer: ZettaScale Zenoh Team,
Installed-Size: 4
Depends: libc6 (>=2.12)
Filename: 0.7.0-rc/libzenohpico_0.7.20221221dev_armhf.deb
Size: 612
MD5sum: 8f6f7e8a4ed8b7e38d7749b1fe5b301a
SHA1: d456ed5b28b8acc8a39e7735afcb39f4578fc6dc
SHA256: 86a24b2422a5b58b1bd9c374f6fa362b29d771424b9530c5eb37f89b9985bb48
Section: devel
Priority: optional
Description: The C client library for Eclipse zenoh targeting pico devices
Package: libzenohpico
Version: 0.7.20221221dev
Architecture: amd64
Maintainer: ZettaScale Zenoh Team,
Installed-Size: 4
Depends: libc6 (>=2.12)
Filename: 0.7.0-rc/libzenohpico_0.7.20221221dev_amd64.deb
Size: 610
MD5sum: 5ac2ab8e131db6e53a637eeeb75f7cb4
SHA1: a9411269770ff19712dcbf74bf362a73aed0643f
SHA256: dbc0aeafcb40edd20334e0730146b47f6aa17ecf8287a8daecfc2157a3376aad
Section: devel
Priority: optional
Description: The C client library for Eclipse zenoh targeting pico devices
Package: libzenohpico
Version: 0.7.20221221dev
Architecture: arm64
Maintainer: ZettaScale Zenoh Team,
Installed-Size: 4
Depends: libc6 (>=2.12)
Filename: 0.7.0-rc/libzenohpico_0.7.20221221dev_arm64.deb
Size: 610
MD5sum: 4f542b2ba0eb0f60996e7c181c96c217
SHA1: 055190b3b29d2904a04df72491f0c2e6e1fc8484
SHA256: 897a3a802f44992980986d9a6f1d6a4bb221d898585d9d9beedf1df8569f6398
Section: devel
Priority: optional
Description: The C client library for Eclipse zenoh targeting pico devices
Package: libzenohpico
Version: 0.7.20221221dev
Architecture: arm
Maintainer: ZettaScale Zenoh Team,
Installed-Size: 4
Depends: libc6 (>=2.12)
Filename: 0.7.0-rc/libzenohpico_0.7.20221221dev_arm.deb
Size: 612
MD5sum: be00f0f47e8cfd042346f8ef3063a51e
SHA1: b148706b9bc252b64696f6ccab3ca2fef12e7b0c
SHA256: 711f855d70925377bbd525699f3874223d978146354aafbfde1cc53fc5a0d79b
Section: devel
Priority: optional
Description: The C client library for Eclipse zenoh targeting pico devices
Package: libzenohpico
Version: 0.7.20221221dev
Architecture: i386
Maintainer: ZettaScale Zenoh Team,
Installed-Size: 4
Depends: libc6 (>=2.12)
Filename: 0.7.0-rc/libzenohpico_0.7.20221221dev_i386.deb
Size: 612
MD5sum: a2f91f9cd89c35894677b14ce7e6c5ea
SHA1: 75e0a177d7e997c6a692978bf030d26a2c3e2dac
SHA256: 532577f3752013424d300021f699d0bb2668e54a4cc42875470947110339d8d0
Section: devel
Priority: optional
Description: The C client library for Eclipse zenoh targeting pico devices
Package: libzenohpico-dev
Version: 0.7.20221221dev
Architecture: i386
Maintainer: ZettaScale Zenoh Team,
Installed-Size: 358
Depends: libzenohpico (=0.7.20221221dev)
Filename: 0.7.0-rc/libzenohpico-dev_0.7.20221221dev_i386.deb
Size: 48602
MD5sum: 3feb136375277b116fdbc66ca4a042f9
SHA1: 2697a3a3e181e9580b0d6aedc2da20a52237b5c7
SHA256: a174ea8acfdab162baf1c942850b3fb868f1ca9e44f76c4dc5cac5b259044751
Section: devel
Priority: optional
Description: The C client library for Eclipse zenoh targeting pico devices - devel files
Package: libzenohpico-dev
Version: 0.7.20221221dev
Architecture: arm64
Maintainer: ZettaScale Zenoh Team,
Installed-Size: 358
Depends: libzenohpico (=0.7.20221221dev)
Filename: 0.7.0-rc/libzenohpico-dev_0.7.20221221dev_arm64.deb
Size: 48604
MD5sum: 0ec0f7821979a1c290e46af962cf56d1
SHA1: c0ae1ad9c9c0f2c195406e74c14586c6da793a7c
SHA256: a5d682479c9fcfef0fc4f3c594a2578a4b748bf12e7ad5dafbb8e3e1f693ec5e
Section: devel
Priority: optional
Description: The C client library for Eclipse zenoh targeting pico devices - devel files
Package: libzenohpico-dev
Version: 0.7.20221221dev
Architecture: arm
Maintainer: ZettaScale Zenoh Team,
Installed-Size: 358
Depends: libzenohpico (=0.7.20221221dev)
Filename: 0.7.0-rc/libzenohpico-dev_0.7.20221221dev_arm.deb
Size: 48606
MD5sum: ef99a8d7298dc7970ba6dbd968ee4608
SHA1: cf13104aa9cf95989187e56667d6c59d4e56cd3b
SHA256: 63e14a145765403b921fb29ab5f0c6bb30b7e203779bf66c4d6afbef19573156
Section: devel
Priority: optional
Description: The C client library for Eclipse zenoh targeting pico devices - devel files
Package: libzenohpico-dev
Version: 0.7.20221221dev
Architecture: mips
Maintainer: ZettaScale Zenoh Team,
Installed-Size: 358
Depends: libzenohpico (=0.7.20221221dev)
Filename: 0.7.0-rc/libzenohpico-dev_0.7.20221221dev_mips.deb
Size: 48602
MD5sum: ea7335a96492c7b98a836cbbb452c7ef
SHA1: d8ff442c20cb1031ca903a28169cdf46482ae66a
SHA256: 845d8a96acb2093413ce21f95de256cf641d6ca5536f9f2550f17c6e0d557ca7
Section: devel
Priority: optional
Description: The C client library for Eclipse zenoh targeting pico devices - devel files
Package: libzenohpico-dev
Version: 0.7.20221221dev
Architecture: amd64
Maintainer: ZettaScale Zenoh Team,
Installed-Size: 358
Depends: libzenohpico (=0.7.20221221dev)
Filename: 0.7.0-rc/libzenohpico-dev_0.7.20221221dev_amd64.deb
Size: 48604
MD5sum: 12776f80ef5c6aea41535dc82c745339
SHA1: d994c6636174cf91440f57d21c422448d78e47d3
SHA256: fcd7ef2c05d33b2cfa66cb0df9231e5d1497e244cdbb04de1e4ee739de65942e
Section: devel
Priority: optional
Description: The C client library for Eclipse zenoh targeting pico devices - devel files
Package: libzenohpico-dev
Version: 0.7.20221221dev
Architecture: armhf
Maintainer: ZettaScale Zenoh Team,
Installed-Size: 358
Depends: libzenohpico (=0.7.20221221dev)
Filename: 0.7.0-rc/libzenohpico-dev_0.7.20221221dev_armhf.deb
Size: 48608
MD5sum: 3427075fb2ccfc7f9b0da401a88d1158
SHA1: 5312994670376187c8dd07ab118a3ceff614429d
SHA256: fa61e88859794d3ff81faee47fd505edde067ffbb61ed4eb60b0bcc44ba376e3
Section: devel
Priority: optional
Description: The C client library for Eclipse zenoh targeting pico devices - devel files
Package: zenoh
Version: 0.7.0-rc
Architecture: arm64
Essential: no
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 1024
Depends: zenohd (=0.7.0-rc), zenoh-plugin-rest (=0.7.0-rc), zenoh-plugin-storage-manager (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh_0.7.0-rc_arm64.deb
Size: 832
MD5sum: 5696a85649ad1faa3732e07e4303f772
SHA1: 5e1767a5489c95da3c4e46ec584c92d0fb03fa19
SHA256: 776385ae4425481fcdf84fdaf4938e3a9ce8ff8b5772676df7e2f04c87377be0
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: The zenoh top-level package
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh
Vcs-Git: https://github.com/eclipse-zenoh/zenoh
Package: zenoh
Version: 0.7.0-rc
Architecture: armel
Essential: no
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 1024
Depends: zenohd (=0.7.0-rc), zenoh-plugin-rest (=0.7.0-rc), zenoh-plugin-storage-manager (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh_0.7.0-rc_armel.deb
Size: 832
MD5sum: 82987a5627a1c66f9e822e2c7fdbd677
SHA1: 9153af98f1fa817a01878db88f94417b886e6c93
SHA256: d33636f6d1d78bdec147a9003ee6918ed8c5868e802136e2e5e05909d4030a40
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: The zenoh top-level package
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh
Vcs-Git: https://github.com/eclipse-zenoh/zenoh
Package: zenoh
Version: 0.7.0-rc
Architecture: amd64
Essential: no
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 1024
Depends: zenohd (=0.7.0-rc), zenoh-plugin-rest (=0.7.0-rc), zenoh-plugin-storage-manager (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh_0.7.0-rc_amd64.deb
Size: 832
MD5sum: d2bd5b3944cecb0bee394ae604b3ad83
SHA1: caefe319bb146e121e50af8c65a8813339ba9520
SHA256: 8cb8dd71feb8caf1c756de1cfdca2686d2ec9df6e749fb33c94bac12c85b9785
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: The zenoh top-level package
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh
Vcs-Git: https://github.com/eclipse-zenoh/zenoh
Package: zenoh
Version: 0.7.0-rc
Architecture: armhf
Essential: no
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 1024
Depends: zenohd (=0.7.0-rc), zenoh-plugin-rest (=0.7.0-rc), zenoh-plugin-storage-manager (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh_0.7.0-rc_armhf.deb
Size: 832
MD5sum: 72572384ffc7462b31fe5486f87eb684
SHA1: c270b94b67483d92df9ef7713d2f5b4c40b3b3b0
SHA256: 327c88da9636726f408534cec6cfef6a0d00980dbef59f1bb73db205b8208429
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: The zenoh top-level package
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh
Vcs-Git: https://github.com/eclipse-zenoh/zenoh
Package: zenoh-backend-filesystem
Version: 0.7.0-rc
Architecture: arm64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 8011
Depends: zenoh-plugin-storage-manager (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-backend-filesystem_0.7.0-rc_arm64.deb
Size: 2391684
MD5sum: 7452feb5bf656879dcbd8dc0470fbf6f
SHA1: 16e4da450a6ae18a92c62ed7d2462b723ce6444a
SHA256: 4db5d7dde17645277687cc7526a7ed97cf2894b779d06a8c1e0b25023ca14b86
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Backend for Zenoh using the file system
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-backend-filesystem
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-backend-filesystem
Package: zenoh-backend-filesystem
Version: 0.7.0-rc
Architecture: armhf
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 6009
Depends: zenoh-plugin-storage-manager (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-backend-filesystem_0.7.0-rc_armhf.deb
Size: 2398372
MD5sum: d12c78193373176fa48f3d8c28bcc134
SHA1: 777ce80e1d8ce275251abe66938f84e411be804f
SHA256: a484c31c71298d580bd76521ee914a66b942fa2e2537fbb725446099f974f5fa
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Backend for Zenoh using the file system
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-backend-filesystem
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-backend-filesystem
Package: zenoh-backend-filesystem
Version: 0.7.0-rc
Architecture: armel
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 7657
Depends: zenoh-plugin-storage-manager (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-backend-filesystem_0.7.0-rc_armel.deb
Size: 2320948
MD5sum: bc6b29fde4332bd98f15c7b752ba2a96
SHA1: 5f5a3d64124200bbc56482b7fe75a9cafaf75094
SHA256: 7b66e0438ac938e023f55ee12d72a14bc2cea4346a1b9a3502b09ca35f45852a
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Backend for Zenoh using the file system
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-backend-filesystem
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-backend-filesystem
Package: zenoh-backend-filesystem
Version: 0.7.0-rc
Architecture: amd64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 9058
Depends: zenoh-plugin-storage-manager (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-backend-filesystem_0.7.0-rc_amd64.deb
Size: 2742356
MD5sum: 427401313bd3ea45f4105cf21b957f44
SHA1: eca152ded035145715852ce163a63e7b1f17587f
SHA256: 85adeb43da5ff12f621c8874dfc6c8761863bf6865fef4e06529754be4eaef69
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Backend for Zenoh using the file system
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-backend-filesystem
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-backend-filesystem
Package: zenoh-backend-influxdb
Version: 0.7.0-rc
Architecture: armhf
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 3849
Depends: zenoh-plugin-storage-manager (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-backend-influxdb_0.7.0-rc_armhf.deb
Size: 1143928
MD5sum: d4bf5f2b4cf445ea8930c2b0366aa177
SHA1: f3b620fcb1c56719d2e1cad59d8882cb73f4cb8e
SHA256: c2c60df4252a7d35aca009328cf2a55a6b625b93cbfcd5d7b1f7fa264dc75b9e
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Backend for Zenoh using InfluxDB
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-backend-influxdb
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-backend-influxdb
Package: zenoh-backend-influxdb
Version: 0.7.0-rc
Architecture: armel
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 3937
Depends: zenoh-plugin-storage-manager (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-backend-influxdb_0.7.0-rc_armel.deb
Size: 1148012
MD5sum: b6628649447c80a01762e06dda89744c
SHA1: f4f07e3af993840292f7e4611c5db3eae5869fb4
SHA256: 740ca9802845b5b3858ef654df50253cb6da4b76b84bd5f4eccbc4a7144aa0b6
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Backend for Zenoh using InfluxDB
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-backend-influxdb
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-backend-influxdb
Package: zenoh-backend-influxdb
Version: 0.7.0-rc
Architecture: amd64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 4938
Depends: zenoh-plugin-storage-manager (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-backend-influxdb_0.7.0-rc_amd64.deb
Size: 1525336
MD5sum: 66faaa994b739be3511183959f030272
SHA1: 06eddfb3917d984d21113c08c05d7377785d9766
SHA256: 000a97127bdbab199165328767e75ea1527df659be779f07e054708f7c4db685
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Backend for Zenoh using InfluxDB
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-backend-influxdb
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-backend-influxdb
Package: zenoh-backend-influxdb
Version: 0.7.0-rc
Architecture: arm64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 4474
Depends: zenoh-plugin-storage-manager (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-backend-influxdb_0.7.0-rc_arm64.deb
Size: 1359060
MD5sum: 1d79b3e97e4932f987d462c4e564d96e
SHA1: 7541febe7adf9615eef337b263f3944316fd2ca8
SHA256: d205739bc69047216a4379b083a3179719f0c66dc0410591d5f42c7517d3cc08
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Backend for Zenoh using InfluxDB
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-backend-influxdb
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-backend-influxdb
Package: zenoh-backend-rocksdb
Version: 0.7.0-rc
Architecture: arm64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 7891
Depends: zenoh-plugin-storage-manager (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-backend-rocksdb_0.7.0-rc_arm64.deb
Size: 2364216
MD5sum: 437cb62d03eefbbcd01435f078267915
SHA1: 4de3ae93b4b33ae76d25cfafc01c32fadbda99a8
SHA256: 09d9472da8bf3cd14aea468b22729c0cf1dfcc1a3a27af709a89b03320a05fe3
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Backend for Zenoh using RocksDB
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-backend-rocksdb
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-backend-rocksdb
Package: zenoh-backend-rocksdb
Version: 0.7.0-rc
Architecture: amd64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 8934
Depends: zenoh-plugin-storage-manager (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-backend-rocksdb_0.7.0-rc_amd64.deb
Size: 2715164
MD5sum: 85f3c0ddf4314c996dad249eab8928dd
SHA1: adcb4a9c2c1e8e65fb2a6a40c9037943e1053051
SHA256: 99692e5a660b34d060d14e2d15b0b250e34bc64b4d4bd85376bc4c93bed15552
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Backend for Zenoh using RocksDB
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-backend-rocksdb
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-backend-rocksdb
Package: zenoh-backend-rocksdb
Version: 0.7.0-rc
Architecture: armhf
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 5917
Depends: zenoh-plugin-storage-manager (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-backend-rocksdb_0.7.0-rc_armhf.deb
Size: 2377568
MD5sum: 62c0d3010cd84e256e4658570c736c9f
SHA1: e34a7249bf73dedeb1edbd85d084dda01114f031
SHA256: a08a415be6058e108a4df78716fc766f628befe9396e8578a2d75c7b0ffcaa2a
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Backend for Zenoh using RocksDB
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-backend-rocksdb
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-backend-rocksdb
Package: zenoh-backend-rocksdb
Version: 0.7.0-rc
Architecture: armel
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 7605
Depends: zenoh-plugin-storage-manager (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-backend-rocksdb_0.7.0-rc_armel.deb
Size: 2301972
MD5sum: 92ffa22727deaebc48c67bac3df5497f
SHA1: ffe5771659c52d704024e37981776d46e6968888
SHA256: bb9db05dfb4e06fb7ff9950f93136f9d6d17d399deda5112769c818b4df83054
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Backend for Zenoh using RocksDB
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-backend-rocksdb
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-backend-rocksdb
Package: zenoh-backend-s3
Version: 0.7.0-rc
Architecture: amd64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 10986
Depends: zenoh-plugin-storage-manager (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-backend-s3_0.7.0-rc_amd64.deb
Size: 2747280
MD5sum: 792bc204beff7f776755ca38ed3c8792
SHA1: b52e7150e0ef1263cf66aa8aff84408dc7c1e8c5
SHA256: 5347b6f211d114e8245b6f22c53c62a2011addda15361d4194823145070a4bd4
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Backend for Zenoh using AWS S3 API
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-backend-s3
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-backend-s3
Package: zenoh-backend-s3
Version: 0.7.0-rc
Architecture: armhf
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 8563
Depends: zenoh-plugin-storage-manager (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-backend-s3_0.7.0-rc_armhf.deb
Size: 2153356
MD5sum: 18deb66c54551e3e175c95af4942b5c6
SHA1: 1a1b8cd418936e95c86868321378c6e8f8263753
SHA256: 569b1471ed45ed81e1e70ab256b7a19d03ac1bf7f3d556d3145d767dffe0496e
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Backend for Zenoh using AWS S3 API
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-backend-s3
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-backend-s3
Package: zenoh-backend-s3
Version: 0.7.0-rc
Architecture: armel
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 8723
Depends: zenoh-plugin-storage-manager (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-backend-s3_0.7.0-rc_armel.deb
Size: 2147588
MD5sum: 0b0148f2132eceab9dfd5e8812fce214
SHA1: 06e7a6d623dcdb680319efc89a7e5009a02163d7
SHA256: 8b48ec42dd096d5df798b769a4b51560f8ade6f34c1506a6124292def6b12392
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Backend for Zenoh using AWS S3 API
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-backend-s3
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-backend-s3
Package: zenoh-backend-s3
Version: 0.7.0-rc
Architecture: arm64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 9806
Depends: zenoh-plugin-storage-manager (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-backend-s3_0.7.0-rc_arm64.deb
Size: 2470960
MD5sum: 5b2e300564c4db2acae9928e6695f9f9
SHA1: 4bcbddc681726057212d74e4e342fe6b46763b1c
SHA256: 2cf89d5b1b5438a80b520d80bf02c67a76cf5db9b94c5b55864b01e1bedc4281
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Backend for Zenoh using AWS S3 API
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-backend-s3
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-backend-s3
Package: zenoh-bridge-dds
Version: 0.7.0-rc
Architecture: armel
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 8072
Filename: 0.7.0-rc/zenoh-bridge-dds_0.7.0-rc_armel.deb
Size: 2573768
MD5sum: 53643143d19bc02f937fb50d264a5cbf
SHA1: b129c7c88d4243c4e19661fe6ce9d9900a26cd67
SHA256: 8c91a529767dc30fd309b3e2bf87dc42d35c4c2ef077e6f5406acb4312f52f99
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Zenoh bridge for ROS2 and DDS in general
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-plugin-dds
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-plugin-dds
Package: zenoh-bridge-dds
Version: 0.7.0-rc
Architecture: amd64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 9174
Depends: libc6 (>= 2.29)
Filename: 0.7.0-rc/zenoh-bridge-dds_0.7.0-rc_amd64.deb
Size: 2959572
MD5sum: ad622f69ccf722f67ae70872c3b05f54
SHA1: a4da5c1ffb03e884315d21e8e3f3032660616e6a
SHA256: 8642a9d9f6da5a08362ffc0ff53091c88dcd9929ea0a35b820195741164edbfd
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Zenoh bridge for ROS2 and DDS in general
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-plugin-dds
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-plugin-dds
Package: zenoh-bridge-dds
Version: 0.7.0-rc
Architecture: arm64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 7921
Filename: 0.7.0-rc/zenoh-bridge-dds_0.7.0-rc_arm64.deb
Size: 2652588
MD5sum: 251e98f8e3cd60ce9febe699fdac0b4f
SHA1: bcd4d405f6697969e9e5e7043442157a20e24541
SHA256: 6ecc1fc876bcceae1377f178bb44d0abaa0599f0642b3284bcacb004b3cc8b51
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Zenoh bridge for ROS2 and DDS in general
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-plugin-dds
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-plugin-dds
Package: zenoh-bridge-dds
Version: 0.7.0-rc
Architecture: armhf
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 7668
Filename: 0.7.0-rc/zenoh-bridge-dds_0.7.0-rc_armhf.deb
Size: 2590408
MD5sum: 49c93609da58aea057eda06d53b60687
SHA1: 6fc8a6228ba300768bdbbb31cbdc50ea6f57f049
SHA256: deaf0a683e7408361572c5deb468c291b76709b81e9550a8333ec6ecc5fdd7b2
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Zenoh bridge for ROS2 and DDS in general
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-plugin-dds
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-plugin-dds
Package: zenoh-bridge-mqtt
Version: 0.7.0-rc
Architecture: amd64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 8277
Depends: libc6 (>= 2.29)
Filename: 0.7.0-rc/zenoh-bridge-mqtt_0.7.0-rc_amd64.deb
Size: 2648100
MD5sum: d652bba7451cc4a58316c2a89feb0cc0
SHA1: 0bb859bfac1f0081474f5dad582537b3c09a8c8c
SHA256: 223ae968996e50ac46e550d36d01155502590d8cc9c1cae8c329f30db9273edd
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Zenoh bridge for MQTT
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-plugin-mqtt
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-plugin-mqtt
Package: zenoh-bridge-mqtt
Version: 0.7.0-rc
Architecture: arm64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 7065
Filename: 0.7.0-rc/zenoh-bridge-mqtt_0.7.0-rc_arm64.deb
Size: 2359492
MD5sum: 90ef64263a3c60ed0e7853d07589e44a
SHA1: 96243881101c495c9dc8da89b7cf80aa4909ac38
SHA256: 570f8b350c0564e73cc215c53cb53361657f0b30ce30b57c41b5d99a68362cd7
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Zenoh bridge for MQTT
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-plugin-mqtt
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-plugin-mqtt
Package: zenoh-plugin-dds
Version: 0.7.0-rc
Architecture: armhf
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 3223
Depends: zenohd (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-plugin-dds_0.7.0-rc_armhf.deb
Size: 1058780
MD5sum: 2d12bd9cc0a8e46c1e765e70a48a0885
SHA1: fe245a2facd4e8b121241d0ce8851c7e78f99f19
SHA256: bb30c701c863203243ba315d6dc9ca503b14797808d018fbf775d1bfccbdf8ed
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Zenoh plugin for ROS2 and DDS in general
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-plugin-dds
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-plugin-dds
Package: zenoh-plugin-dds
Version: 0.7.0-rc
Architecture: armel
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 3503
Depends: zenohd (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-plugin-dds_0.7.0-rc_armel.deb
Size: 1048948
MD5sum: b49451cbc6099ebb980890ec5690f4aa
SHA1: 5780dab9c110639c576e77eb6f952d11b17abac2
SHA256: 6f3a518b6718e4d28a6d8ff40bea841c694d40410b1781bc1b9b10bddbf29650
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Zenoh plugin for ROS2 and DDS in general
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-plugin-dds
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-plugin-dds
Package: zenoh-plugin-dds
Version: 0.7.0-rc
Architecture: amd64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 4076
Depends: zenohd (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-plugin-dds_0.7.0-rc_amd64.deb
Size: 1213400
MD5sum: 1da523f4e75f6f0b08cb19acc8d9615b
SHA1: 79daae99b983e3db39d877554b2317dbb02d74c0
SHA256: 08fd7a3fc60258f77abff128d37e5f14ff953a263d706960265005b29435ef8d
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Zenoh plugin for ROS2 and DDS in general
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-plugin-dds
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-plugin-dds
Package: zenoh-plugin-dds
Version: 0.7.0-rc
Architecture: arm64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 3652
Depends: zenohd (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-plugin-dds_0.7.0-rc_arm64.deb
Size: 1078136
MD5sum: 3156709fd3ecfda4920d63321d76b29b
SHA1: e37eb306e0c9bb2a82bf86ac0fdc5f1483b7e86f
SHA256: ca428283d68d767dc7e9d2233126358b63b81accdca59f69379b73e896c0719c
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Zenoh plugin for ROS2 and DDS in general
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-plugin-dds
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-plugin-dds
Package: zenoh-plugin-mqtt
Version: 0.7.0-rc
Architecture: arm64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 2802
Depends: zenohd (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-plugin-mqtt_0.7.0-rc_arm64.deb
Size: 780372
MD5sum: c1ed6276f1bb40c5b8fa25bc480d5376
SHA1: f57e12a21e0f33cab422ab00713ad72a9821d536
SHA256: 19b30afcf01b1d8039a8a03a560adf0d212f46a729c4c397e104f27e595a2149
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Zenoh plugin for MQTT
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-plugin-mqtt
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-plugin-mqtt
Package: zenoh-plugin-mqtt
Version: 0.7.0-rc
Architecture: amd64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 3194
Depends: zenohd (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-plugin-mqtt_0.7.0-rc_amd64.deb
Size: 899012
MD5sum: be9241bb2575af2c855001a8dc9fca80
SHA1: 5031400c58e63dadc4611f08b1e7809f5cc3c905
SHA256: 6106c6a8a8a6c386cc8db0767c3c0fb39f2473cf2ae96eaec478a29fdbd4f642
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Zenoh plugin for MQTT
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-plugin-mqtt
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-plugin-mqtt
Package: zenoh-plugin-rest
Version: 0.7.0-rc
Architecture: arm64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 2846
Depends: zenohd (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-plugin-rest_0.7.0-rc_arm64.deb
Size: 806356
MD5sum: 5181e0b3fe8fac1d5d3ccf329c3fdb82
SHA1: e0a6df0b952036de604580d44a5690a144a9bd90
SHA256: 20f271adbdae2458afa1e140ff567ad3318e32a6c1c07a6e81ba3a6a17d5cbcc
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: The zenoh REST plugin
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh
Vcs-Git: https://github.com/eclipse-zenoh/zenoh
Package: zenoh-plugin-rest
Version: 0.7.0-rc
Architecture: amd64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 3210
Depends: zenohd (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-plugin-rest_0.7.0-rc_amd64.deb
Size: 916224
MD5sum: ee03a17e5bb39c4fb7d33d04f4d0aced
SHA1: f996303333320c0e7c14ff0a9ee26e4ab7c1f1bd
SHA256: b3b63fedcab65833171dde9692b5c55f526c65cb7d9ea060ae0d32796040f8aa
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: The zenoh REST plugin
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh
Vcs-Git: https://github.com/eclipse-zenoh/zenoh
Package: zenoh-plugin-rest
Version: 0.7.0-rc
Architecture: armel
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 2765
Depends: zenohd (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-plugin-rest_0.7.0-rc_armel.deb
Size: 802520
MD5sum: fa5ef5feb976681e949c0df7fba10b1f
SHA1: 9b2f453318bc3e293e829420d224a2b43de0309b
SHA256: 3bc19155d64899ee28920c68d9b4d6beeb3e18ff7f795160135e1a03e43cbba7
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: The zenoh REST plugin
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh
Vcs-Git: https://github.com/eclipse-zenoh/zenoh
Package: zenoh-plugin-rest
Version: 0.7.0-rc
Architecture: armhf
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 2709
Depends: zenohd (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-plugin-rest_0.7.0-rc_armhf.deb
Size: 796356
MD5sum: 6b6979fb58b4f07714f9e170fd60991b
SHA1: e8bdd487139f90b6a23f55be25638002ba9cc5bc
SHA256: 9c5dfb41616aee1bd34a992ae2f3473aada67143a06aa90703b8cb54aa9d1de0
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: The zenoh REST plugin
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh
Vcs-Git: https://github.com/eclipse-zenoh/zenoh
Package: zenoh-plugin-storage-manager
Version: 0.7.0-rc
Architecture: arm64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 2766
Depends: zenohd (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-plugin-storage-manager_0.7.0-rc_arm64.deb
Size: 774748
MD5sum: bc1fc381153681314d349ca11e0479eb
SHA1: 031511c7ca9e720e2dd372697f497c1aad347e7a
SHA256: 5851e5e913e7abfd68c2701bf806fc330487759b33fb9b44c19c474067a9fd48
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: The zenoh storages plugin.
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh
Vcs-Git: https://github.com/eclipse-zenoh/zenoh
Package: zenoh-plugin-storage-manager
Version: 0.7.0-rc
Architecture: armel
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 2721
Depends: zenohd (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-plugin-storage-manager_0.7.0-rc_armel.deb
Size: 783096
MD5sum: 849764317289c3090722fbf5f5e140ec
SHA1: c2e211ce27c9d9983acbba634332fe351a11d165
SHA256: e2e6f96510d2ccdf46d83df1607f1fc26397485d16653148d078f5a48c411a29
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: The zenoh storages plugin.
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh
Vcs-Git: https://github.com/eclipse-zenoh/zenoh
Package: zenoh-plugin-storage-manager
Version: 0.7.0-rc
Architecture: armhf
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 2661
Depends: zenohd (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-plugin-storage-manager_0.7.0-rc_armhf.deb
Size: 776108
MD5sum: 80440c49ba92597d75b3c8b6124afaf2
SHA1: b897317caa92f7de3f19c70034d6a40ba5dc047c
SHA256: cd15117da03b7e1dd48b8a8d9ed786bf62067c385d868afd7f2591c8c5476a59
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: The zenoh storages plugin.
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh
Vcs-Git: https://github.com/eclipse-zenoh/zenoh
Package: zenoh-plugin-storage-manager
Version: 0.7.0-rc
Architecture: amd64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 3170
Depends: zenohd (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-plugin-storage-manager_0.7.0-rc_amd64.deb
Size: 891748
MD5sum: a7b1670f23f926ca20265aee46503e8a
SHA1: 99e418d6eeb0b2c1101f3e45f16ca38810c778fd
SHA256: 62fd5b5f662f8c6dbd7caaf4a4e8de8f71dd92fd4f980ea8b81c4f230878f629
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: The zenoh storages plugin.
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh
Vcs-Git: https://github.com/eclipse-zenoh/zenoh
Package: zenoh-plugin-webserver
Version: 0.7.0-rc
Architecture: arm64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 4162
Depends: zenohd (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-plugin-webserver_0.7.0-rc_arm64.deb
Size: 1064200
MD5sum: 1a0bef27a3b5ed08c820b06ef564c79b
SHA1: f38e4fb04358cb27527a409f0a7a8ffb6ce2c71c
SHA256: 77e136161ce42761f271f5863ba5624955d70d0da3d5595b51ddf909a071bd65
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Plugin for Zenoh implementing an HTTP server that maps URLs to zenoh key
expressions
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-plugin-webserver
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-plugin-webserver
Package: zenoh-plugin-webserver
Version: 0.7.0-rc
Architecture: armhf
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 3681
Depends: zenohd (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-plugin-webserver_0.7.0-rc_armhf.deb
Size: 981260
MD5sum: ae79fb22a8166c9db7c0fa9decfacf61
SHA1: 52cba97c757fb961f2c756a69de5d4bd0296cd24
SHA256: 44ada5a965b4e314bf6a66aeca23eec85c35c848a4316a33e6a7d562fcc69645
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Plugin for Zenoh implementing an HTTP server that maps URLs to zenoh key
expressions
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-plugin-webserver
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-plugin-webserver
Package: zenoh-plugin-webserver
Version: 0.7.0-rc
Architecture: amd64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 4390
Depends: zenohd (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-plugin-webserver_0.7.0-rc_amd64.deb
Size: 1182512
MD5sum: e5efe1817870a5b53c02b4d5316d2776
SHA1: a1b6a352f8155e0388445a285b0d9b135922e2ab
SHA256: c2a065a8913026e6549db0484b00224ed7384a8e26e3ae8f543473855c070c87
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Plugin for Zenoh implementing an HTTP server that maps URLs to zenoh key
expressions
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-plugin-webserver
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-plugin-webserver
Package: zenoh-plugin-webserver
Version: 0.7.0-rc
Architecture: armel
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 3769
Depends: zenohd (=0.7.0-rc)
Filename: 0.7.0-rc/zenoh-plugin-webserver_0.7.0-rc_armel.deb
Size: 990120
MD5sum: 3a10bad34ebfec749b788fb016b7b11f
SHA1: 0ec4bfda0da438ae0c4c8370a8c73a2102df0ca2
SHA256: ff2292ce822fba5f7a8fe5372ab1bf1cac853acf3e20515b5a4929922ec6d67d
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Plugin for Zenoh implementing an HTTP server that maps URLs to zenoh key
expressions
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-plugin-webserver
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-plugin-webserver
Package: zenohd
Version: 0.7.0-rc
Architecture: armhf
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 5869
Depends: libc6:armhf (>= 2.31)
Filename: 0.7.0-rc/zenohd_0.7.0-rc_armhf.deb
Size: 1904524
MD5sum: a0e528368776695a96ed8b2a9e36d2a1
SHA1: 21f9814bee8ea9a5fa0bd56e2b8b83dc398556aa
SHA256: ccc8100112927ab3a5d732ca97c20fa8c262133fb0752bd3530bb15d9f1e328f
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Zenoh: Zero Overhead Pub/sub, Store/Query and Compute.
.
[](https://github.com/eclipse-zenoh/zenoh/actions?query=workflow%3A%22CI%22)
[](https://zenoh-rust.readthedocs.io/en/latest/?badge=latest)
[](https://github.com/eclipse-zenoh/roadmap/discussions)
[](https://discord.gg/2GJ958VuHs)
[](https://choosealicense.com/licenses/epl-2.0/)
[](https://opensource.org/licenses/Apache-2.0)
.
# Eclipse Zenoh
The Eclipse Zenoh: Zero Overhead Pub/sub, Store/Query and Compute.
.
Zenoh (pronounce _/zeno/_) unifies data in motion, data at rest and
computations. It carefully blends traditional pub/sub with geo-distributed
storages, queries and computations, while retaining a level of time and space
efficiency that is well beyond any of the mainstream stacks.
.
Check the website [zenoh.io](http://zenoh.io) and the
[roadmap](https://github.com/eclipse-zenoh/roadmap) for more detailed
information.
.
-------------------------------
## Getting Started
.
Zenoh is extremely easy to learn, the best place to master the fundamentals is
our [getting started guide](https://zenoh.io/docs/getting-started/first-app/).
.
-------------------------------
## How to install it
.
To install the latest release of the Zenoh router (`zenohd`) and its default
plugins (REST API plugin and Storages Manager plugin) you can do as follows:
.
### Manual installation (all platforms)
.
All release packages can be downloaded from:
- https://download.eclipse.org/zenoh/zenoh/latest/
.
Each subdirectory has the name of the Rust target. See the platforms each
target corresponds to on
https://doc.rust-lang.org/stable/rustc/platform-support.html
.
Choose your platform and download the `.zip` file.
Unzip it where you want, and run the extracted `zenohd` binary.
.
### Linux Debian
.
Add Eclipse Zenoh private repository to the sources list, and install the
`zenoh` package:
.
```bash
echo "deb [trusted=yes] https://download.eclipse.org/zenoh/debian-repo/ /" |
sudo tee -a /etc/apt/sources.list > /dev/null
sudo apt update
sudo apt install zenoh
```
Then you can start run `zenohd`.
.
### MacOS
.
Tap our brew package repository and install the `zenoh` formula:
.
```bash
brew tap eclipse-zenoh/homebrew-zenoh
brew install zenoh
```
Then you can start run `zenohd`.
.
.
### Rust API
.
-------------------------------
## How to build it
.
> :warning: **WARNING** :warning: : Zenoh and its ecosystem are under active
development. When you build from git, make sure you also build from git any
other Zenoh repository you plan to use (e.g. binding, plugin, backend, etc.).
It may happen that some changes in git are not compatible with the most recent
packaged Zenoh release (e.g. deb, docker, pip). We put particular effort in
mantaining compatibility between the various git repositories in the Zenoh
project.
.
Install [Cargo and
Rust](https://doc.rust-lang.org/cargo/getting-started/installation.html). Zenoh
can be succesfully compiled with Rust stable (>= 1.62.1), so no special
configuration is required from your side.
To build Zenoh, just type the following command after having followed the
previous instructions:
.
```bash
$ cargo build --release --all-targets
```
.
Zenoh's router is built as `target/release/zenohd`. All the examples are built
into the `target/release/examples` directory. They can all work in
peer-to-peer, or interconnected via the zenoh router.
.
-------------------------------
## Previous 0.5 API:
The following documentation pertains to the v0.6 API, which comes many changes
to the behaviour and configuration of Zenoh.
.
To access the v0.5 version of the code and matching README, please go to the
[0.5.0-beta.9](https://github.com/eclipse-zenoh/zenoh/tree/0.5.0-beta.9) tagged
version.
.
-------------------------------
## Quick tests of your build:
.
**Peer-to-peer tests:**
.
- **pub/sub**
- run: `./target/release/examples/z_sub`
- in another shell run: `./target/release/examples/z_put`
- the subscriber should receive the publication.
.
- **get/queryable**
- run: `./target/release/examples/z_queryable`
- in another shell run: `./target/release/examples/z_get`
- the queryable should display the log in its listener, and the get should
receive the queryable result.
.
**Routed tests:**
.
- **put/store/get**
- run the Zenoh router with a memory storage:
`./target/release/zenohd
--cfg='plugins/storage_manager/storages/demo:{key_expr:"demo/example/**",volume:"memory"}'`
- in another shell run: `./target/release/examples/z_put`
- then run `./target/release/examples/z_get`
- the get should receive the stored publication.
.
- **REST API using `curl` tool**
- run the Zenoh router with a memory storage:
`./target/release/zenohd
--cfg='plugins/storage_manager/storages/demo:{key_expr:"demo/example/**",volume:"memory"}'`
- in another shell, do a publication via the REST API:
`curl -X PUT -d 'Hello World!' http://localhost:8000/demo/example/test`
- get it back via the REST API:
`curl http://localhost:8000/demo/example/test`
.
- **router admin space via the REST API**
- run the Zenoh router with permission to perform config changes via the
admin space, and with a memory storage:
`./target/release/zenohd --adminspace-permissions=rw
--cfg='plugins/storage_manager/storages/demo:{key_expr:"demo/example/**",volume:"memory"}'`
- in another shell, get info of the zenoh router via the zenoh admin space:
.
`curl http://localhost:8000/@/router/local`
- get the volumes of the router (only memory by default):
`curl 'http://localhost:8000/@/router/local/**/volumes/*'`
- get the storages of the local router (the memory storage configured at
startup on '/demo/example/**' should be present):
`curl 'http://localhost:8000/@/router/local/**/storages/*'`
- add another memory storage on `/demo/mystore/**`:
`curl -X PUT -H 'content-type:application/json' -d
'{"key_expr":"demo/mystore/**","volume":"memory"}'
http://localhost:8000/@/router/local/config/plugins/storage_manager/storages/mystore`
- check it has been created:
`curl 'http://localhost:8000/@/router/local/**/storages/*'`
.
.
See other examples of Zenoh usage in [examples/](examples)
.
-------------------------------
## Zenoh router command line arguments
`zenohd` accepts the following arguments:
.
* `--adminspace-permissions <[r|w|rw|none]>`: Configure the read and/or write
permissions on the admin space. Default is read only.
* `-c, --config `: a [JSON5](https://json5.org) configuration file.
[DEFAULT_CONFIG.json5](DEFAULT_CONFIG.json5) shows the schema of this file. All
properties of this configuration are optional, so you may not need such a large
configuration for your use-case.
* `--cfg :` : allows you to change specific parts of the
configuration right after it has been constructed. VALUE must be a valid JSON5
value, and key must be a path through the configuration file, where each
element is separated by a `/`. When inserting in parts of the config that are
arrays, you may use indexes, or may use `+` to indicate that you want to append
your value to the array. `--cfg` passed values will always override any
previously existing value for their key in the configuration.
* `-l, --listen ...`: An endpoint on which this router will listen
for incoming sessions.
Repeat this option to open several listeners. By default, `tcp/[::]:7447`
is used. The following endpoints are currently supported:
- TCP: `tcp/:`
- UDP: `udp/:`
- [TCP+TLS](https://zenoh.io/docs/manual/tls/): `tls/:`
- [QUIC](https://zenoh.io/docs/manual/quic/): `quic/:`
* `-e, --connect ...`: An endpoint this router will try to connect
to. Repeat this option to connect to several peers or routers.
* `--no-multicast-scouting`: By default zenohd replies to multicast scouting
messages for being discovered by peers and clients.
This option disables this feature.
* `-i, --id `: The identifier (as an hexadecimal string - e.g.:
0A0B23...) that zenohd must use.
**WARNING**: this identifier must be unique in the system! If not set, a
random UUIDv4 will be used.
* `--no-timestamp`: By default zenohd adds a HLC-generated Timestamp to each
routed Data if there isn't already one.
This option disables this feature.
* `-P, --plugin [ | :]...`: A
[plugin](https://zenoh.io/docs/manual/plugins/) that must be loaded. Accepted
values:
- a plugin name; zenohd will search for a library named
`libzplugin_.so` on Unix, `libzplugin_.dylib` on MacOS or
`zplugin_.dll` on Windows.
- `":"`; the plugin will be loaded from library
file at ``.
.
Repeat this option to load several plugins.
* `--plugin-search-dir ...`: A directory where to search for
[plugins](https://zenoh.io/docs/manual/plugins/) libraries to load.
Repeat this option to specify several search directories'. By default, the
plugins libraries will be searched in:
`'/usr/local/lib:/usr/lib:~/.zenoh/lib:.'`
* `--rest-http-port `: Configures the [REST
plugin](https://zenoh.io/docs/manual/plugin-http/)'s HTTP port. Accepted
values:
- a port number
- a string with format `:` (to bind the HTTP
server to a specific interface)
- `"None"` to desactivate the REST plugin
.
If not specified, the REST plugin will be active on any interface (`[::]`)
and port `8000`.
.
-------------------------------
## Plugins
By default the Zenoh router is delivered or built with 2 plugins. These may be
configured through a configuration file, or through individual changes to the
configuration via the `--cfg` CLI option or via zenoh puts on individual parts
of the configuration.
.
WARNING: since `v0.6`, `zenohd` no longer loads every available plugin at
startup. Instead, only configured plugins are loaded (after processing `--cfg`
and `--plugin` options). Once `zenohd` is running, plugins can be hot-loaded
and, if they support it, reconfigured at runtime by editing their configuration
through the adminspace.
.
Note that the REST plugin is added to the configuration by the default value of
the `--rest-http-port` CLI argument.
.
**[REST plugin](https://zenoh.io/docs/manual/plugin-http/)** (exposing a REST
API):
This plugin converts GET and PUT REST requests into Zenoh gets and puts
respectively.
.
**[Storages plugin](https://zenoh.io/docs/manual/plugin-storages/)** (managing
[backends and storages](https://zenoh.io/docs/manual/backends/))
This plugin allows you to easily define storages. These will store key-value
pairs they subscribed to, and send the most recent ones when queried. Check out
[DEFAULT_CONFIG.json5](DEFAULT_CONFIG.json5) for info on how to configure them.
.
-------------------------------
## Troubleshooting
.
In case of troubles, please first check on [this
page](https://zenoh.io/docs/getting-started/troubleshooting/) if the trouble
and cause are already known.
Otherwise, you can ask a question on the [zenoh Discord
server](https://discord.gg/vSDSpqnbkm), or [create an
issue](https://github.com/eclipse-zenoh/zenoh/issues).
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh
Vcs-Git: https://github.com/eclipse-zenoh/zenoh
Package: zenohd
Version: 0.7.0-rc
Architecture: arm64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 5857
Depends: libc6:arm64 (>= 2.31)
Filename: 0.7.0-rc/zenohd_0.7.0-rc_arm64.deb
Size: 1956868
MD5sum: 3f6ac79e4cbbe6e6ae3f5d77330b0980
SHA1: 386da910ed3ee53bea74c8bebdbf06e5ccd54669
SHA256: 8e7ffc4eacfee283dcb372af75dded8c4ac57095e9842d6126d109e37e629d36
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Zenoh: Zero Overhead Pub/sub, Store/Query and Compute.
.
[](https://github.com/eclipse-zenoh/zenoh/actions?query=workflow%3A%22CI%22)
[](https://zenoh-rust.readthedocs.io/en/latest/?badge=latest)
[](https://github.com/eclipse-zenoh/roadmap/discussions)
[](https://discord.gg/2GJ958VuHs)
[](https://choosealicense.com/licenses/epl-2.0/)
[](https://opensource.org/licenses/Apache-2.0)
.
# Eclipse Zenoh
The Eclipse Zenoh: Zero Overhead Pub/sub, Store/Query and Compute.
.
Zenoh (pronounce _/zeno/_) unifies data in motion, data at rest and
computations. It carefully blends traditional pub/sub with geo-distributed
storages, queries and computations, while retaining a level of time and space
efficiency that is well beyond any of the mainstream stacks.
.
Check the website [zenoh.io](http://zenoh.io) and the
[roadmap](https://github.com/eclipse-zenoh/roadmap) for more detailed
information.
.
-------------------------------
## Getting Started
.
Zenoh is extremely easy to learn, the best place to master the fundamentals is
our [getting started guide](https://zenoh.io/docs/getting-started/first-app/).
.
-------------------------------
## How to install it
.
To install the latest release of the Zenoh router (`zenohd`) and its default
plugins (REST API plugin and Storages Manager plugin) you can do as follows:
.
### Manual installation (all platforms)
.
All release packages can be downloaded from:
- https://download.eclipse.org/zenoh/zenoh/latest/
.
Each subdirectory has the name of the Rust target. See the platforms each
target corresponds to on
https://doc.rust-lang.org/stable/rustc/platform-support.html
.
Choose your platform and download the `.zip` file.
Unzip it where you want, and run the extracted `zenohd` binary.
.
### Linux Debian
.
Add Eclipse Zenoh private repository to the sources list, and install the
`zenoh` package:
.
```bash
echo "deb [trusted=yes] https://download.eclipse.org/zenoh/debian-repo/ /" |
sudo tee -a /etc/apt/sources.list > /dev/null
sudo apt update
sudo apt install zenoh
```
Then you can start run `zenohd`.
.
### MacOS
.
Tap our brew package repository and install the `zenoh` formula:
.
```bash
brew tap eclipse-zenoh/homebrew-zenoh
brew install zenoh
```
Then you can start run `zenohd`.
.
.
### Rust API
.
-------------------------------
## How to build it
.
> :warning: **WARNING** :warning: : Zenoh and its ecosystem are under active
development. When you build from git, make sure you also build from git any
other Zenoh repository you plan to use (e.g. binding, plugin, backend, etc.).
It may happen that some changes in git are not compatible with the most recent
packaged Zenoh release (e.g. deb, docker, pip). We put particular effort in
mantaining compatibility between the various git repositories in the Zenoh
project.
.
Install [Cargo and
Rust](https://doc.rust-lang.org/cargo/getting-started/installation.html). Zenoh
can be succesfully compiled with Rust stable (>= 1.62.1), so no special
configuration is required from your side.
To build Zenoh, just type the following command after having followed the
previous instructions:
.
```bash
$ cargo build --release --all-targets
```
.
Zenoh's router is built as `target/release/zenohd`. All the examples are built
into the `target/release/examples` directory. They can all work in
peer-to-peer, or interconnected via the zenoh router.
.
-------------------------------
## Previous 0.5 API:
The following documentation pertains to the v0.6 API, which comes many changes
to the behaviour and configuration of Zenoh.
.
To access the v0.5 version of the code and matching README, please go to the
[0.5.0-beta.9](https://github.com/eclipse-zenoh/zenoh/tree/0.5.0-beta.9) tagged
version.
.
-------------------------------
## Quick tests of your build:
.
**Peer-to-peer tests:**
.
- **pub/sub**
- run: `./target/release/examples/z_sub`
- in another shell run: `./target/release/examples/z_put`
- the subscriber should receive the publication.
.
- **get/queryable**
- run: `./target/release/examples/z_queryable`
- in another shell run: `./target/release/examples/z_get`
- the queryable should display the log in its listener, and the get should
receive the queryable result.
.
**Routed tests:**
.
- **put/store/get**
- run the Zenoh router with a memory storage:
`./target/release/zenohd
--cfg='plugins/storage_manager/storages/demo:{key_expr:"demo/example/**",volume:"memory"}'`
- in another shell run: `./target/release/examples/z_put`
- then run `./target/release/examples/z_get`
- the get should receive the stored publication.
.
- **REST API using `curl` tool**
- run the Zenoh router with a memory storage:
`./target/release/zenohd
--cfg='plugins/storage_manager/storages/demo:{key_expr:"demo/example/**",volume:"memory"}'`
- in another shell, do a publication via the REST API:
`curl -X PUT -d 'Hello World!' http://localhost:8000/demo/example/test`
- get it back via the REST API:
`curl http://localhost:8000/demo/example/test`
.
- **router admin space via the REST API**
- run the Zenoh router with permission to perform config changes via the
admin space, and with a memory storage:
`./target/release/zenohd --adminspace-permissions=rw
--cfg='plugins/storage_manager/storages/demo:{key_expr:"demo/example/**",volume:"memory"}'`
- in another shell, get info of the zenoh router via the zenoh admin space:
.
`curl http://localhost:8000/@/router/local`
- get the volumes of the router (only memory by default):
`curl 'http://localhost:8000/@/router/local/**/volumes/*'`
- get the storages of the local router (the memory storage configured at
startup on '/demo/example/**' should be present):
`curl 'http://localhost:8000/@/router/local/**/storages/*'`
- add another memory storage on `/demo/mystore/**`:
`curl -X PUT -H 'content-type:application/json' -d
'{"key_expr":"demo/mystore/**","volume":"memory"}'
http://localhost:8000/@/router/local/config/plugins/storage_manager/storages/mystore`
- check it has been created:
`curl 'http://localhost:8000/@/router/local/**/storages/*'`
.
.
See other examples of Zenoh usage in [examples/](examples)
.
-------------------------------
## Zenoh router command line arguments
`zenohd` accepts the following arguments:
.
* `--adminspace-permissions <[r|w|rw|none]>`: Configure the read and/or write
permissions on the admin space. Default is read only.
* `-c, --config `: a [JSON5](https://json5.org) configuration file.
[DEFAULT_CONFIG.json5](DEFAULT_CONFIG.json5) shows the schema of this file. All
properties of this configuration are optional, so you may not need such a large
configuration for your use-case.
* `--cfg :` : allows you to change specific parts of the
configuration right after it has been constructed. VALUE must be a valid JSON5
value, and key must be a path through the configuration file, where each
element is separated by a `/`. When inserting in parts of the config that are
arrays, you may use indexes, or may use `+` to indicate that you want to append
your value to the array. `--cfg` passed values will always override any
previously existing value for their key in the configuration.
* `-l, --listen ...`: An endpoint on which this router will listen
for incoming sessions.
Repeat this option to open several listeners. By default, `tcp/[::]:7447`
is used. The following endpoints are currently supported:
- TCP: `tcp/:`
- UDP: `udp/:`
- [TCP+TLS](https://zenoh.io/docs/manual/tls/): `tls/:`
- [QUIC](https://zenoh.io/docs/manual/quic/): `quic/:`
* `-e, --connect ...`: An endpoint this router will try to connect
to. Repeat this option to connect to several peers or routers.
* `--no-multicast-scouting`: By default zenohd replies to multicast scouting
messages for being discovered by peers and clients.
This option disables this feature.
* `-i, --id `: The identifier (as an hexadecimal string - e.g.:
0A0B23...) that zenohd must use.
**WARNING**: this identifier must be unique in the system! If not set, a
random UUIDv4 will be used.
* `--no-timestamp`: By default zenohd adds a HLC-generated Timestamp to each
routed Data if there isn't already one.
This option disables this feature.
* `-P, --plugin [ | :]...`: A
[plugin](https://zenoh.io/docs/manual/plugins/) that must be loaded. Accepted
values:
- a plugin name; zenohd will search for a library named
`libzplugin_.so` on Unix, `libzplugin_.dylib` on MacOS or
`zplugin_.dll` on Windows.
- `":"`; the plugin will be loaded from library
file at ``.
.
Repeat this option to load several plugins.
* `--plugin-search-dir ...`: A directory where to search for
[plugins](https://zenoh.io/docs/manual/plugins/) libraries to load.
Repeat this option to specify several search directories'. By default, the
plugins libraries will be searched in:
`'/usr/local/lib:/usr/lib:~/.zenoh/lib:.'`
* `--rest-http-port `: Configures the [REST
plugin](https://zenoh.io/docs/manual/plugin-http/)'s HTTP port. Accepted
values:
- a port number
- a string with format `:` (to bind the HTTP
server to a specific interface)
- `"None"` to desactivate the REST plugin
.
If not specified, the REST plugin will be active on any interface (`[::]`)
and port `8000`.
.
-------------------------------
## Plugins
By default the Zenoh router is delivered or built with 2 plugins. These may be
configured through a configuration file, or through individual changes to the
configuration via the `--cfg` CLI option or via zenoh puts on individual parts
of the configuration.
.
WARNING: since `v0.6`, `zenohd` no longer loads every available plugin at
startup. Instead, only configured plugins are loaded (after processing `--cfg`
and `--plugin` options). Once `zenohd` is running, plugins can be hot-loaded
and, if they support it, reconfigured at runtime by editing their configuration
through the adminspace.
.
Note that the REST plugin is added to the configuration by the default value of
the `--rest-http-port` CLI argument.
.
**[REST plugin](https://zenoh.io/docs/manual/plugin-http/)** (exposing a REST
API):
This plugin converts GET and PUT REST requests into Zenoh gets and puts
respectively.
.
**[Storages plugin](https://zenoh.io/docs/manual/plugin-storages/)** (managing
[backends and storages](https://zenoh.io/docs/manual/backends/))
This plugin allows you to easily define storages. These will store key-value
pairs they subscribed to, and send the most recent ones when queried. Check out
[DEFAULT_CONFIG.json5](DEFAULT_CONFIG.json5) for info on how to configure them.
.
-------------------------------
## Troubleshooting
.
In case of troubles, please first check on [this
page](https://zenoh.io/docs/getting-started/troubleshooting/) if the trouble
and cause are already known.
Otherwise, you can ask a question on the [zenoh Discord
server](https://discord.gg/vSDSpqnbkm), or [create an
issue](https://github.com/eclipse-zenoh/zenoh/issues).
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh
Vcs-Git: https://github.com/eclipse-zenoh/zenoh
Package: zenohd
Version: 0.7.0-rc
Architecture: amd64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 6945
Depends: libc6 (>= 2.28)
Filename: 0.7.0-rc/zenohd_0.7.0-rc_amd64.deb
Size: 2209372
MD5sum: ae0c195da70b3a0fde9163c58133f090
SHA1: eaf19324be6ca2557a5ca070e82eeb48befe8dce
SHA256: 27fbf4588d97d9d5bff0281ff6ceaac83a4c7e4f6e1245da824f96a969de68d8
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Zenoh: Zero Overhead Pub/sub, Store/Query and Compute.
.
[](https://github.com/eclipse-zenoh/zenoh/actions?query=workflow%3A%22CI%22)
[](https://zenoh-rust.readthedocs.io/en/latest/?badge=latest)
[](https://github.com/eclipse-zenoh/roadmap/discussions)
[](https://discord.gg/2GJ958VuHs)
[](https://choosealicense.com/licenses/epl-2.0/)
[](https://opensource.org/licenses/Apache-2.0)
.
# Eclipse Zenoh
The Eclipse Zenoh: Zero Overhead Pub/sub, Store/Query and Compute.
.
Zenoh (pronounce _/zeno/_) unifies data in motion, data at rest and
computations. It carefully blends traditional pub/sub with geo-distributed
storages, queries and computations, while retaining a level of time and space
efficiency that is well beyond any of the mainstream stacks.
.
Check the website [zenoh.io](http://zenoh.io) and the
[roadmap](https://github.com/eclipse-zenoh/roadmap) for more detailed
information.
.
-------------------------------
## Getting Started
.
Zenoh is extremely easy to learn, the best place to master the fundamentals is
our [getting started guide](https://zenoh.io/docs/getting-started/first-app/).
.
-------------------------------
## How to install it
.
To install the latest release of the Zenoh router (`zenohd`) and its default
plugins (REST API plugin and Storages Manager plugin) you can do as follows:
.
### Manual installation (all platforms)
.
All release packages can be downloaded from:
- https://download.eclipse.org/zenoh/zenoh/latest/
.
Each subdirectory has the name of the Rust target. See the platforms each
target corresponds to on
https://doc.rust-lang.org/stable/rustc/platform-support.html
.
Choose your platform and download the `.zip` file.
Unzip it where you want, and run the extracted `zenohd` binary.
.
### Linux Debian
.
Add Eclipse Zenoh private repository to the sources list, and install the
`zenoh` package:
.
```bash
echo "deb [trusted=yes] https://download.eclipse.org/zenoh/debian-repo/ /" |
sudo tee -a /etc/apt/sources.list > /dev/null
sudo apt update
sudo apt install zenoh
```
Then you can start run `zenohd`.
.
### MacOS
.
Tap our brew package repository and install the `zenoh` formula:
.
```bash
brew tap eclipse-zenoh/homebrew-zenoh
brew install zenoh
```
Then you can start run `zenohd`.
.
.
### Rust API
.
-------------------------------
## How to build it
.
> :warning: **WARNING** :warning: : Zenoh and its ecosystem are under active
development. When you build from git, make sure you also build from git any
other Zenoh repository you plan to use (e.g. binding, plugin, backend, etc.).
It may happen that some changes in git are not compatible with the most recent
packaged Zenoh release (e.g. deb, docker, pip). We put particular effort in
mantaining compatibility between the various git repositories in the Zenoh
project.
.
Install [Cargo and
Rust](https://doc.rust-lang.org/cargo/getting-started/installation.html). Zenoh
can be succesfully compiled with Rust stable (>= 1.62.1), so no special
configuration is required from your side.
To build Zenoh, just type the following command after having followed the
previous instructions:
.
```bash
$ cargo build --release --all-targets
```
.
Zenoh's router is built as `target/release/zenohd`. All the examples are built
into the `target/release/examples` directory. They can all work in
peer-to-peer, or interconnected via the zenoh router.
.
-------------------------------
## Previous 0.5 API:
The following documentation pertains to the v0.6 API, which comes many changes
to the behaviour and configuration of Zenoh.
.
To access the v0.5 version of the code and matching README, please go to the
[0.5.0-beta.9](https://github.com/eclipse-zenoh/zenoh/tree/0.5.0-beta.9) tagged
version.
.
-------------------------------
## Quick tests of your build:
.
**Peer-to-peer tests:**
.
- **pub/sub**
- run: `./target/release/examples/z_sub`
- in another shell run: `./target/release/examples/z_put`
- the subscriber should receive the publication.
.
- **get/queryable**
- run: `./target/release/examples/z_queryable`
- in another shell run: `./target/release/examples/z_get`
- the queryable should display the log in its listener, and the get should
receive the queryable result.
.
**Routed tests:**
.
- **put/store/get**
- run the Zenoh router with a memory storage:
`./target/release/zenohd
--cfg='plugins/storage_manager/storages/demo:{key_expr:"demo/example/**",volume:"memory"}'`
- in another shell run: `./target/release/examples/z_put`
- then run `./target/release/examples/z_get`
- the get should receive the stored publication.
.
- **REST API using `curl` tool**
- run the Zenoh router with a memory storage:
`./target/release/zenohd
--cfg='plugins/storage_manager/storages/demo:{key_expr:"demo/example/**",volume:"memory"}'`
- in another shell, do a publication via the REST API:
`curl -X PUT -d 'Hello World!' http://localhost:8000/demo/example/test`
- get it back via the REST API:
`curl http://localhost:8000/demo/example/test`
.
- **router admin space via the REST API**
- run the Zenoh router with permission to perform config changes via the
admin space, and with a memory storage:
`./target/release/zenohd --adminspace-permissions=rw
--cfg='plugins/storage_manager/storages/demo:{key_expr:"demo/example/**",volume:"memory"}'`
- in another shell, get info of the zenoh router via the zenoh admin space:
.
`curl http://localhost:8000/@/router/local`
- get the volumes of the router (only memory by default):
`curl 'http://localhost:8000/@/router/local/**/volumes/*'`
- get the storages of the local router (the memory storage configured at
startup on '/demo/example/**' should be present):
`curl 'http://localhost:8000/@/router/local/**/storages/*'`
- add another memory storage on `/demo/mystore/**`:
`curl -X PUT -H 'content-type:application/json' -d
'{"key_expr":"demo/mystore/**","volume":"memory"}'
http://localhost:8000/@/router/local/config/plugins/storage_manager/storages/mystore`
- check it has been created:
`curl 'http://localhost:8000/@/router/local/**/storages/*'`
.
.
See other examples of Zenoh usage in [examples/](examples)
.
-------------------------------
## Zenoh router command line arguments
`zenohd` accepts the following arguments:
.
* `--adminspace-permissions <[r|w|rw|none]>`: Configure the read and/or write
permissions on the admin space. Default is read only.
* `-c, --config `: a [JSON5](https://json5.org) configuration file.
[DEFAULT_CONFIG.json5](DEFAULT_CONFIG.json5) shows the schema of this file. All
properties of this configuration are optional, so you may not need such a large
configuration for your use-case.
* `--cfg :` : allows you to change specific parts of the
configuration right after it has been constructed. VALUE must be a valid JSON5
value, and key must be a path through the configuration file, where each
element is separated by a `/`. When inserting in parts of the config that are
arrays, you may use indexes, or may use `+` to indicate that you want to append
your value to the array. `--cfg` passed values will always override any
previously existing value for their key in the configuration.
* `-l, --listen ...`: An endpoint on which this router will listen
for incoming sessions.
Repeat this option to open several listeners. By default, `tcp/[::]:7447`
is used. The following endpoints are currently supported:
- TCP: `tcp/:`
- UDP: `udp/:`
- [TCP+TLS](https://zenoh.io/docs/manual/tls/): `tls/:`
- [QUIC](https://zenoh.io/docs/manual/quic/): `quic/:`
* `-e, --connect ...`: An endpoint this router will try to connect
to. Repeat this option to connect to several peers or routers.
* `--no-multicast-scouting`: By default zenohd replies to multicast scouting
messages for being discovered by peers and clients.
This option disables this feature.
* `-i, --id `: The identifier (as an hexadecimal string - e.g.:
0A0B23...) that zenohd must use.
**WARNING**: this identifier must be unique in the system! If not set, a
random UUIDv4 will be used.
* `--no-timestamp`: By default zenohd adds a HLC-generated Timestamp to each
routed Data if there isn't already one.
This option disables this feature.
* `-P, --plugin [ | :]...`: A
[plugin](https://zenoh.io/docs/manual/plugins/) that must be loaded. Accepted
values:
- a plugin name; zenohd will search for a library named
`libzplugin_.so` on Unix, `libzplugin_.dylib` on MacOS or
`zplugin_.dll` on Windows.
- `":"`; the plugin will be loaded from library
file at ``.
.
Repeat this option to load several plugins.
* `--plugin-search-dir ...`: A directory where to search for
[plugins](https://zenoh.io/docs/manual/plugins/) libraries to load.
Repeat this option to specify several search directories'. By default, the
plugins libraries will be searched in:
`'/usr/local/lib:/usr/lib:~/.zenoh/lib:.'`
* `--rest-http-port `: Configures the [REST
plugin](https://zenoh.io/docs/manual/plugin-http/)'s HTTP port. Accepted
values:
- a port number
- a string with format `:` (to bind the HTTP
server to a specific interface)
- `"None"` to desactivate the REST plugin
.
If not specified, the REST plugin will be active on any interface (`[::]`)
and port `8000`.
.
-------------------------------
## Plugins
By default the Zenoh router is delivered or built with 2 plugins. These may be
configured through a configuration file, or through individual changes to the
configuration via the `--cfg` CLI option or via zenoh puts on individual parts
of the configuration.
.
WARNING: since `v0.6`, `zenohd` no longer loads every available plugin at
startup. Instead, only configured plugins are loaded (after processing `--cfg`
and `--plugin` options). Once `zenohd` is running, plugins can be hot-loaded
and, if they support it, reconfigured at runtime by editing their configuration
through the adminspace.
.
Note that the REST plugin is added to the configuration by the default value of
the `--rest-http-port` CLI argument.
.
**[REST plugin](https://zenoh.io/docs/manual/plugin-http/)** (exposing a REST
API):
This plugin converts GET and PUT REST requests into Zenoh gets and puts
respectively.
.
**[Storages plugin](https://zenoh.io/docs/manual/plugin-storages/)** (managing
[backends and storages](https://zenoh.io/docs/manual/backends/))
This plugin allows you to easily define storages. These will store key-value
pairs they subscribed to, and send the most recent ones when queried. Check out
[DEFAULT_CONFIG.json5](DEFAULT_CONFIG.json5) for info on how to configure them.
.
-------------------------------
## Troubleshooting
.
In case of troubles, please first check on [this
page](https://zenoh.io/docs/getting-started/troubleshooting/) if the trouble
and cause are already known.
Otherwise, you can ask a question on the [zenoh Discord
server](https://discord.gg/vSDSpqnbkm), or [create an
issue](https://github.com/eclipse-zenoh/zenoh/issues).
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh
Vcs-Git: https://github.com/eclipse-zenoh/zenoh
Package: zenohd
Version: 0.7.0-rc
Architecture: armel
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 6025
Depends: libc6:armel (>= 2.31)
Filename: 0.7.0-rc/zenohd_0.7.0-rc_armel.deb
Size: 1905136
MD5sum: 606ab2748d05ffa7c358eea6d812361c
SHA1: 911e6a69a0e14c20ac9d9a8b249b1eb877272108
SHA256: 5ab3d318704697227d15fefa851641da12ea4275345e2ae93e3eb8dd6557a2fc
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Zenoh: Zero Overhead Pub/sub, Store/Query and Compute.
.
[](https://github.com/eclipse-zenoh/zenoh/actions?query=workflow%3A%22CI%22)
[](https://zenoh-rust.readthedocs.io/en/latest/?badge=latest)
[](https://github.com/eclipse-zenoh/roadmap/discussions)
[](https://discord.gg/2GJ958VuHs)
[](https://choosealicense.com/licenses/epl-2.0/)
[](https://opensource.org/licenses/Apache-2.0)
.
# Eclipse Zenoh
The Eclipse Zenoh: Zero Overhead Pub/sub, Store/Query and Compute.
.
Zenoh (pronounce _/zeno/_) unifies data in motion, data at rest and
computations. It carefully blends traditional pub/sub with geo-distributed
storages, queries and computations, while retaining a level of time and space
efficiency that is well beyond any of the mainstream stacks.
.
Check the website [zenoh.io](http://zenoh.io) and the
[roadmap](https://github.com/eclipse-zenoh/roadmap) for more detailed
information.
.
-------------------------------
## Getting Started
.
Zenoh is extremely easy to learn, the best place to master the fundamentals is
our [getting started guide](https://zenoh.io/docs/getting-started/first-app/).
.
-------------------------------
## How to install it
.
To install the latest release of the Zenoh router (`zenohd`) and its default
plugins (REST API plugin and Storages Manager plugin) you can do as follows:
.
### Manual installation (all platforms)
.
All release packages can be downloaded from:
- https://download.eclipse.org/zenoh/zenoh/latest/
.
Each subdirectory has the name of the Rust target. See the platforms each
target corresponds to on
https://doc.rust-lang.org/stable/rustc/platform-support.html
.
Choose your platform and download the `.zip` file.
Unzip it where you want, and run the extracted `zenohd` binary.
.
### Linux Debian
.
Add Eclipse Zenoh private repository to the sources list, and install the
`zenoh` package:
.
```bash
echo "deb [trusted=yes] https://download.eclipse.org/zenoh/debian-repo/ /" |
sudo tee -a /etc/apt/sources.list > /dev/null
sudo apt update
sudo apt install zenoh
```
Then you can start run `zenohd`.
.
### MacOS
.
Tap our brew package repository and install the `zenoh` formula:
.
```bash
brew tap eclipse-zenoh/homebrew-zenoh
brew install zenoh
```
Then you can start run `zenohd`.
.
.
### Rust API
.
-------------------------------
## How to build it
.
> :warning: **WARNING** :warning: : Zenoh and its ecosystem are under active
development. When you build from git, make sure you also build from git any
other Zenoh repository you plan to use (e.g. binding, plugin, backend, etc.).
It may happen that some changes in git are not compatible with the most recent
packaged Zenoh release (e.g. deb, docker, pip). We put particular effort in
mantaining compatibility between the various git repositories in the Zenoh
project.
.
Install [Cargo and
Rust](https://doc.rust-lang.org/cargo/getting-started/installation.html). Zenoh
can be succesfully compiled with Rust stable (>= 1.62.1), so no special
configuration is required from your side.
To build Zenoh, just type the following command after having followed the
previous instructions:
.
```bash
$ cargo build --release --all-targets
```
.
Zenoh's router is built as `target/release/zenohd`. All the examples are built
into the `target/release/examples` directory. They can all work in
peer-to-peer, or interconnected via the zenoh router.
.
-------------------------------
## Previous 0.5 API:
The following documentation pertains to the v0.6 API, which comes many changes
to the behaviour and configuration of Zenoh.
.
To access the v0.5 version of the code and matching README, please go to the
[0.5.0-beta.9](https://github.com/eclipse-zenoh/zenoh/tree/0.5.0-beta.9) tagged
version.
.
-------------------------------
## Quick tests of your build:
.
**Peer-to-peer tests:**
.
- **pub/sub**
- run: `./target/release/examples/z_sub`
- in another shell run: `./target/release/examples/z_put`
- the subscriber should receive the publication.
.
- **get/queryable**
- run: `./target/release/examples/z_queryable`
- in another shell run: `./target/release/examples/z_get`
- the queryable should display the log in its listener, and the get should
receive the queryable result.
.
**Routed tests:**
.
- **put/store/get**
- run the Zenoh router with a memory storage:
`./target/release/zenohd
--cfg='plugins/storage_manager/storages/demo:{key_expr:"demo/example/**",volume:"memory"}'`
- in another shell run: `./target/release/examples/z_put`
- then run `./target/release/examples/z_get`
- the get should receive the stored publication.
.
- **REST API using `curl` tool**
- run the Zenoh router with a memory storage:
`./target/release/zenohd
--cfg='plugins/storage_manager/storages/demo:{key_expr:"demo/example/**",volume:"memory"}'`
- in another shell, do a publication via the REST API:
`curl -X PUT -d 'Hello World!' http://localhost:8000/demo/example/test`
- get it back via the REST API:
`curl http://localhost:8000/demo/example/test`
.
- **router admin space via the REST API**
- run the Zenoh router with permission to perform config changes via the
admin space, and with a memory storage:
`./target/release/zenohd --adminspace-permissions=rw
--cfg='plugins/storage_manager/storages/demo:{key_expr:"demo/example/**",volume:"memory"}'`
- in another shell, get info of the zenoh router via the zenoh admin space:
.
`curl http://localhost:8000/@/router/local`
- get the volumes of the router (only memory by default):
`curl 'http://localhost:8000/@/router/local/**/volumes/*'`
- get the storages of the local router (the memory storage configured at
startup on '/demo/example/**' should be present):
`curl 'http://localhost:8000/@/router/local/**/storages/*'`
- add another memory storage on `/demo/mystore/**`:
`curl -X PUT -H 'content-type:application/json' -d
'{"key_expr":"demo/mystore/**","volume":"memory"}'
http://localhost:8000/@/router/local/config/plugins/storage_manager/storages/mystore`
- check it has been created:
`curl 'http://localhost:8000/@/router/local/**/storages/*'`
.
.
See other examples of Zenoh usage in [examples/](examples)
.
-------------------------------
## Zenoh router command line arguments
`zenohd` accepts the following arguments:
.
* `--adminspace-permissions <[r|w|rw|none]>`: Configure the read and/or write
permissions on the admin space. Default is read only.
* `-c, --config `: a [JSON5](https://json5.org) configuration file.
[DEFAULT_CONFIG.json5](DEFAULT_CONFIG.json5) shows the schema of this file. All
properties of this configuration are optional, so you may not need such a large
configuration for your use-case.
* `--cfg :` : allows you to change specific parts of the
configuration right after it has been constructed. VALUE must be a valid JSON5
value, and key must be a path through the configuration file, where each
element is separated by a `/`. When inserting in parts of the config that are
arrays, you may use indexes, or may use `+` to indicate that you want to append
your value to the array. `--cfg` passed values will always override any
previously existing value for their key in the configuration.
* `-l, --listen ...`: An endpoint on which this router will listen
for incoming sessions.
Repeat this option to open several listeners. By default, `tcp/[::]:7447`
is used. The following endpoints are currently supported:
- TCP: `tcp/:`
- UDP: `udp/:`
- [TCP+TLS](https://zenoh.io/docs/manual/tls/): `tls/:`
- [QUIC](https://zenoh.io/docs/manual/quic/): `quic/:`
* `-e, --connect ...`: An endpoint this router will try to connect
to. Repeat this option to connect to several peers or routers.
* `--no-multicast-scouting`: By default zenohd replies to multicast scouting
messages for being discovered by peers and clients.
This option disables this feature.
* `-i, --id `: The identifier (as an hexadecimal string - e.g.:
0A0B23...) that zenohd must use.
**WARNING**: this identifier must be unique in the system! If not set, a
random UUIDv4 will be used.
* `--no-timestamp`: By default zenohd adds a HLC-generated Timestamp to each
routed Data if there isn't already one.
This option disables this feature.
* `-P, --plugin [ | :]...`: A
[plugin](https://zenoh.io/docs/manual/plugins/) that must be loaded. Accepted
values:
- a plugin name; zenohd will search for a library named
`libzplugin_.so` on Unix, `libzplugin_.dylib` on MacOS or
`zplugin_.dll` on Windows.
- `":"`; the plugin will be loaded from library
file at ``.
.
Repeat this option to load several plugins.
* `--plugin-search-dir ...`: A directory where to search for
[plugins](https://zenoh.io/docs/manual/plugins/) libraries to load.
Repeat this option to specify several search directories'. By default, the
plugins libraries will be searched in:
`'/usr/local/lib:/usr/lib:~/.zenoh/lib:.'`
* `--rest-http-port `: Configures the [REST
plugin](https://zenoh.io/docs/manual/plugin-http/)'s HTTP port. Accepted
values:
- a port number
- a string with format `:` (to bind the HTTP
server to a specific interface)
- `"None"` to desactivate the REST plugin
.
If not specified, the REST plugin will be active on any interface (`[::]`)
and port `8000`.
.
-------------------------------
## Plugins
By default the Zenoh router is delivered or built with 2 plugins. These may be
configured through a configuration file, or through individual changes to the
configuration via the `--cfg` CLI option or via zenoh puts on individual parts
of the configuration.
.
WARNING: since `v0.6`, `zenohd` no longer loads every available plugin at
startup. Instead, only configured plugins are loaded (after processing `--cfg`
and `--plugin` options). Once `zenohd` is running, plugins can be hot-loaded
and, if they support it, reconfigured at runtime by editing their configuration
through the adminspace.
.
Note that the REST plugin is added to the configuration by the default value of
the `--rest-http-port` CLI argument.
.
**[REST plugin](https://zenoh.io/docs/manual/plugin-http/)** (exposing a REST
API):
This plugin converts GET and PUT REST requests into Zenoh gets and puts
respectively.
.
**[Storages plugin](https://zenoh.io/docs/manual/plugin-storages/)** (managing
[backends and storages](https://zenoh.io/docs/manual/backends/))
This plugin allows you to easily define storages. These will store key-value
pairs they subscribed to, and send the most recent ones when queried. Check out
[DEFAULT_CONFIG.json5](DEFAULT_CONFIG.json5) for info on how to configure them.
.
-------------------------------
## Troubleshooting
.
In case of troubles, please first check on [this
page](https://zenoh.io/docs/getting-started/troubleshooting/) if the trouble
and cause are already known.
Otherwise, you can ask a question on the [zenoh Discord
server](https://discord.gg/vSDSpqnbkm), or [create an
issue](https://github.com/eclipse-zenoh/zenoh/issues).
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh
Vcs-Git: https://github.com/eclipse-zenoh/zenoh