Package: libzenohc
Version: 0.6.0~beta.1
Architecture: armel
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 9938
Depends: libc6:armel (>= 2.31)
Filename: 0.6.0-beta.1/libzenohc_0.6.0~beta.1_armel.deb
Size: 2625640
MD5sum: ec8014dee0986c144663676ad6ec4dc3
SHA1: 7e94629561638fd5f9da7dd35466d443c77efb7d
SHA256: f64a5af2a143f9157f2cef85d23aafadf95f0cb13fb565b56e92d57e1d4a89b9
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/vSDSpqnbkm)
[](https://choosealicense.com/licenses/epl-2.0/)
[](https://opensource.org/licenses/Apache-2.0)
.
.
# Eclipse zenoh C Client API
.
[Eclipse zenoh](http://zenoh.io) is an extremely efficient and fault-tolerant
[Named Data Networking](http://named-data.net) (NDN) protocol
that is able to scale down to extremely constrainded devices and networks.
.
Check the website [zenoh.io](http://zenoh.io) and the
[roadmap](https://github.com/eclipse-zenoh/roadmap) for more detailed
information.
.
-------------------------------
## How to build it
.
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 rust
```
.
[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.6.0~beta.1
Architecture: amd64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 10726
Depends: libc6 (>= 2.28)
Filename: 0.6.0-beta.1/libzenohc_0.6.0~beta.1_amd64.deb
Size: 2870524
MD5sum: 8c40c820718cddac6fb0a3ff6a881fa0
SHA1: 343c836ff68559cb464a116a10a9197553331fb1
SHA256: 5a0ecb6f7e383da7fcd1c68bc1c1e8ec001a9a6fb6b3c80ab740e4ebb18c40a1
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/vSDSpqnbkm)
[](https://choosealicense.com/licenses/epl-2.0/)
[](https://opensource.org/licenses/Apache-2.0)
.
.
# Eclipse zenoh C Client API
.
[Eclipse zenoh](http://zenoh.io) is an extremely efficient and fault-tolerant
[Named Data Networking](http://named-data.net) (NDN) protocol
that is able to scale down to extremely constrainded devices and networks.
.
Check the website [zenoh.io](http://zenoh.io) and the
[roadmap](https://github.com/eclipse-zenoh/roadmap) for more detailed
information.
.
-------------------------------
## How to build it
.
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 rust
```
.
[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.6.0~beta.1
Architecture: armhf
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 9798
Depends: libc6:armhf (>= 2.31)
Filename: 0.6.0-beta.1/libzenohc_0.6.0~beta.1_armhf.deb
Size: 2630252
MD5sum: cb3870284ecd5900ed558039ba3dee1a
SHA1: a6ac6f97864dd5b1ef60e6985b3f5c69426d2b4f
SHA256: ef8fa33419f04679b43a28b5a518fd07afc25377974d8496cf998046c3c8fab7
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/vSDSpqnbkm)
[](https://choosealicense.com/licenses/epl-2.0/)
[](https://opensource.org/licenses/Apache-2.0)
.
.
# Eclipse zenoh C Client API
.
[Eclipse zenoh](http://zenoh.io) is an extremely efficient and fault-tolerant
[Named Data Networking](http://named-data.net) (NDN) protocol
that is able to scale down to extremely constrainded devices and networks.
.
Check the website [zenoh.io](http://zenoh.io) and the
[roadmap](https://github.com/eclipse-zenoh/roadmap) for more detailed
information.
.
-------------------------------
## How to build it
.
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 rust
```
.
[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.6.0~beta.1
Architecture: arm64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 9584
Depends: libc6:arm64 (>= 2.31)
Filename: 0.6.0-beta.1/libzenohc_0.6.0~beta.1_arm64.deb
Size: 2570328
MD5sum: 4b57ad079f9b86ea416fd7674a6c8ca5
SHA1: e1499771b7b058ecef1d68731d47fba12718cb15
SHA256: 3135bd05ce7520476d18a4096c3665792d8ff3309ddd82f781d2a6e13d13b63e
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/vSDSpqnbkm)
[](https://choosealicense.com/licenses/epl-2.0/)
[](https://opensource.org/licenses/Apache-2.0)
.
.
# Eclipse zenoh C Client API
.
[Eclipse zenoh](http://zenoh.io) is an extremely efficient and fault-tolerant
[Named Data Networking](http://named-data.net) (NDN) protocol
that is able to scale down to extremely constrainded devices and networks.
.
Check the website [zenoh.io](http://zenoh.io) and the
[roadmap](https://github.com/eclipse-zenoh/roadmap) for more detailed
information.
.
-------------------------------
## How to build it
.
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 rust
```
.
[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.6.0~beta.1
Architecture: armel
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 99
Depends: libzenohc (=0.6.0~dev)
Filename: 0.6.0-beta.1/libzenohc-dev_0.6.0~beta.1_armel.deb
Size: 21020
MD5sum: 814c6e2626e62b920c6781ba507dedbd
SHA1: 7aab40967ec7123b12382f29accb3e3076f5e9bd
SHA256: aae39816e6da56fd699c98588810dfbfb1b3de30d37fee1e4cf3e79df6cc6c72
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/vSDSpqnbkm)
[](https://choosealicense.com/licenses/epl-2.0/)
[](https://opensource.org/licenses/Apache-2.0)
.
.
# Eclipse zenoh C Client API
.
[Eclipse zenoh](http://zenoh.io) is an extremely efficient and fault-tolerant
[Named Data Networking](http://named-data.net) (NDN) protocol
that is able to scale down to extremely constrainded devices and networks.
.
Check the website [zenoh.io](http://zenoh.io) and the
[roadmap](https://github.com/eclipse-zenoh/roadmap) for more detailed
information.
.
-------------------------------
## How to build it
.
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 rust
```
.
[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.6.0~beta.1
Architecture: amd64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 99
Depends: libzenohc (=0.6.0~dev)
Filename: 0.6.0-beta.1/libzenohc-dev_0.6.0~beta.1_amd64.deb
Size: 21020
MD5sum: 3a6df27d9c725338c9ab63fa072badb3
SHA1: 743b2b7571162ccd7bba6f8a9997c5148c4d6f76
SHA256: 03686b548a50c6c944fb85fe8f76ba6673acfbca916f0f5ac0d798c4ce29f8ed
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/vSDSpqnbkm)
[](https://choosealicense.com/licenses/epl-2.0/)
[](https://opensource.org/licenses/Apache-2.0)
.
.
# Eclipse zenoh C Client API
.
[Eclipse zenoh](http://zenoh.io) is an extremely efficient and fault-tolerant
[Named Data Networking](http://named-data.net) (NDN) protocol
that is able to scale down to extremely constrainded devices and networks.
.
Check the website [zenoh.io](http://zenoh.io) and the
[roadmap](https://github.com/eclipse-zenoh/roadmap) for more detailed
information.
.
-------------------------------
## How to build it
.
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 rust
```
.
[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.6.0~beta.1
Architecture: armhf
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 99
Depends: libzenohc (=0.6.0~dev)
Filename: 0.6.0-beta.1/libzenohc-dev_0.6.0~beta.1_armhf.deb
Size: 21012
MD5sum: d34df53f888bfef6859fcdbe7631ad12
SHA1: 8b0681f03e9a40179a179ed04fde9005fb04f018
SHA256: 71d0e5fec061c5cfadef239e1f6087f37f2fdb1bb4b3550c28a44f7aed1928c5
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/vSDSpqnbkm)
[](https://choosealicense.com/licenses/epl-2.0/)
[](https://opensource.org/licenses/Apache-2.0)
.
.
# Eclipse zenoh C Client API
.
[Eclipse zenoh](http://zenoh.io) is an extremely efficient and fault-tolerant
[Named Data Networking](http://named-data.net) (NDN) protocol
that is able to scale down to extremely constrainded devices and networks.
.
Check the website [zenoh.io](http://zenoh.io) and the
[roadmap](https://github.com/eclipse-zenoh/roadmap) for more detailed
information.
.
-------------------------------
## How to build it
.
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 rust
```
.
[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.6.0~beta.1
Architecture: arm64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 99
Depends: libzenohc (=0.6.0~dev)
Filename: 0.6.0-beta.1/libzenohc-dev_0.6.0~beta.1_arm64.deb
Size: 21008
MD5sum: c573d12c530bfd08290598731823516d
SHA1: 8da1aebed402aa56dd228032dfb71f5d0a6f3557
SHA256: 34ae99bafd3ecc126fb91e976951323bf1012dd3944b299756c96665e2a1c52d
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/vSDSpqnbkm)
[](https://choosealicense.com/licenses/epl-2.0/)
[](https://opensource.org/licenses/Apache-2.0)
.
.
# Eclipse zenoh C Client API
.
[Eclipse zenoh](http://zenoh.io) is an extremely efficient and fault-tolerant
[Named Data Networking](http://named-data.net) (NDN) protocol
that is able to scale down to extremely constrainded devices and networks.
.
Check the website [zenoh.io](http://zenoh.io) and the
[roadmap](https://github.com/eclipse-zenoh/roadmap) for more detailed
information.
.
-------------------------------
## How to build it
.
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 rust
```
.
[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.6.20220929dev
Architecture: i386
Maintainer: ZettaScale Zenoh Team,
Installed-Size: 4
Depends: libc6 (>=2.12)
Filename: 0.6.0-beta.1/libzenohpico_0.6.20220929dev_i386.deb
Size: 608
MD5sum: 1222e7998d741bc4d11c67c50ea8241c
SHA1: daf50c649a8502984f277644ea546cfe5b5f7de4
SHA256: 1aef814c51b28ddae550d0f58cb696d9d074ccf3c95d59a161d07783c202b001
Section: devel
Priority: optional
Description: The C client library for Eclipse zenoh targeting pico devices
Package: libzenohpico
Version: 0.6.20220929dev
Architecture: amd64
Maintainer: ZettaScale Zenoh Team,
Installed-Size: 4
Depends: libc6 (>=2.12)
Filename: 0.6.0-beta.1/libzenohpico_0.6.20220929dev_amd64.deb
Size: 608
MD5sum: 25213de3333eef1e1169177dfc5a1409
SHA1: 8c8b03dbf6630493004ccaca3a71cafe46c5ba42
SHA256: 08be143ec5e9c387df3f600f0d2b3076610c75991ae9018da96670caa6f25069
Section: devel
Priority: optional
Description: The C client library for Eclipse zenoh targeting pico devices
Package: libzenohpico
Version: 0.6.20220929dev
Architecture: armhf
Maintainer: ZettaScale Zenoh Team,
Installed-Size: 4
Depends: libc6 (>=2.12)
Filename: 0.6.0-beta.1/libzenohpico_0.6.20220929dev_armhf.deb
Size: 610
MD5sum: 74176c7ccdb2ed267039658292550e58
SHA1: 8051b39a07ca40f49c312f7ea35ee7a2b6c0f85f
SHA256: 7513e0e44503408c8531fa688e457a08422cf0aba87b07a37909af7ac39a3d70
Section: devel
Priority: optional
Description: The C client library for Eclipse zenoh targeting pico devices
Package: libzenohpico
Version: 0.6.20220929dev
Architecture: arm
Maintainer: ZettaScale Zenoh Team,
Installed-Size: 4
Depends: libc6 (>=2.12)
Filename: 0.6.0-beta.1/libzenohpico_0.6.20220929dev_arm.deb
Size: 606
MD5sum: e72f4f7aff6314a426503bd02863cdf8
SHA1: 5ba8578f9afe6d82533de91ec2b5f6534f509d36
SHA256: 61fce3e36db1c315830f9fdce88b569118212ed787639722b728498ebdf6d70d
Section: devel
Priority: optional
Description: The C client library for Eclipse zenoh targeting pico devices
Package: libzenohpico
Version: 0.6.20220929dev
Architecture: mips
Maintainer: ZettaScale Zenoh Team,
Installed-Size: 4
Depends: libc6 (>=2.12)
Filename: 0.6.0-beta.1/libzenohpico_0.6.20220929dev_mips.deb
Size: 608
MD5sum: 53a8d260d548a37e96738deb803ac2e1
SHA1: 1a51faf19721cad94a1277f2c44a97c66418cb26
SHA256: 4a87fbf2e01a2fbe5694e4fec6e73b00192691d46f6b40bff4f73fc6a54ea1fc
Section: devel
Priority: optional
Description: The C client library for Eclipse zenoh targeting pico devices
Package: libzenohpico
Version: 0.6.20220929dev
Architecture: arm64
Maintainer: ZettaScale Zenoh Team,
Installed-Size: 4
Depends: libc6 (>=2.12)
Filename: 0.6.0-beta.1/libzenohpico_0.6.20220929dev_arm64.deb
Size: 610
MD5sum: 1ffb05a7d44ec3463150f91db327ca6d
SHA1: 8376466ea8a1068eb87c8edfbeb78174eabf8e5f
SHA256: 498fc81b2c01bb9214eafc55a53bdbc29fe2e9b295ebe2c10969b685b42ff997
Section: devel
Priority: optional
Description: The C client library for Eclipse zenoh targeting pico devices
Package: libzenohpico-dev
Version: 0.6.20220929dev
Architecture: i386
Maintainer: ZettaScale Zenoh Team,
Installed-Size: 344
Depends: libzenohpico (=0.6.20220929dev)
Filename: 0.6.0-beta.1/libzenohpico-dev_0.6.20220929dev_i386.deb
Size: 47018
MD5sum: da4f47ce7be35f4f5d062a63bc6bb6fe
SHA1: 35c024a97696860a297b5355acfdf6d463f7e5f8
SHA256: 99695b5ad60bf44211788fdeb1804cc26d2f53bb082499b8f2dffd47604365e1
Section: devel
Priority: optional
Description: The C client library for Eclipse zenoh targeting pico devices - devel files
Package: libzenohpico-dev
Version: 0.6.20220929dev
Architecture: arm
Maintainer: ZettaScale Zenoh Team,
Installed-Size: 344
Depends: libzenohpico (=0.6.20220929dev)
Filename: 0.6.0-beta.1/libzenohpico-dev_0.6.20220929dev_arm.deb
Size: 47018
MD5sum: 092129851ece9d9791a31034f5707977
SHA1: ff56a4cfbc6561ebb2f5a470e79d3482e246eb81
SHA256: 34a75549df72b3e79036dda64e0976a27a2b8ff1401c482aab5acccfb352e308
Section: devel
Priority: optional
Description: The C client library for Eclipse zenoh targeting pico devices - devel files
Package: libzenohpico-dev
Version: 0.6.20220929dev
Architecture: armhf
Maintainer: ZettaScale Zenoh Team,
Installed-Size: 344
Depends: libzenohpico (=0.6.20220929dev)
Filename: 0.6.0-beta.1/libzenohpico-dev_0.6.20220929dev_armhf.deb
Size: 47028
MD5sum: 7022f5180373eed4e8c868c9b9ad4505
SHA1: adff60ca173e3fc06700d7849f706e264af934de
SHA256: 83fe19c64fbab7801e0cd1381feb3bbb71f154ed468bbb3096a10b9997caa800
Section: devel
Priority: optional
Description: The C client library for Eclipse zenoh targeting pico devices - devel files
Package: libzenohpico-dev
Version: 0.6.20220929dev
Architecture: arm64
Maintainer: ZettaScale Zenoh Team,
Installed-Size: 344
Depends: libzenohpico (=0.6.20220929dev)
Filename: 0.6.0-beta.1/libzenohpico-dev_0.6.20220929dev_arm64.deb
Size: 47028
MD5sum: bba7cb0680d6f56f5e6784d4f098b267
SHA1: d13e784bf50aa8164d5477a175da8d66af91684d
SHA256: 3be0175ef6001523eafa6fbe6fb3acd0e76fda3ac28012162ae7303c2385cd2e
Section: devel
Priority: optional
Description: The C client library for Eclipse zenoh targeting pico devices - devel files
Package: libzenohpico-dev
Version: 0.6.20220929dev
Architecture: amd64
Maintainer: ZettaScale Zenoh Team,
Installed-Size: 344
Depends: libzenohpico (=0.6.20220929dev)
Filename: 0.6.0-beta.1/libzenohpico-dev_0.6.20220929dev_amd64.deb
Size: 47028
MD5sum: 413ee9a2fb14341de06fb502fd800aea
SHA1: 4712b4f146f037c2d0846986bd3dd5b40e5a480d
SHA256: 672b22158f1552da12e262b616cd269d1ee08f1f6d8d46947c823f3f73d5273d
Section: devel
Priority: optional
Description: The C client library for Eclipse zenoh targeting pico devices - devel files
Package: libzenohpico-dev
Version: 0.6.20220929dev
Architecture: mips
Maintainer: ZettaScale Zenoh Team,
Installed-Size: 344
Depends: libzenohpico (=0.6.20220929dev)
Filename: 0.6.0-beta.1/libzenohpico-dev_0.6.20220929dev_mips.deb
Size: 47028
MD5sum: 9c9f910bea25d83ad521e36c7ab548d7
SHA1: c8d076d92e54d107babd7e5ebb92fa2fe2c609c6
SHA256: 60488a17db956e257af62849dc19c630b5bfb7c10ed533c79ec6d05c775d1465
Section: devel
Priority: optional
Description: The C client library for Eclipse zenoh targeting pico devices - devel files
Package: zenoh
Version: 0.6.0~beta.1
Architecture: amd64
Essential: no
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 1024
Depends: zenohd (=0.6.0~beta.1), zenoh-plugin-rest (=0.6.0~beta.1), zenoh-plugin-storage-manager (=0.6.0~beta.1)
Filename: 0.6.0-beta.1/zenoh_0.6.0~beta.1_amd64.deb
Size: 836
MD5sum: a1de2e9b80224819786ac0e5ceb64021
SHA1: 363e1d12ce35bff7c8e53fb875c8ac4110d288ef
SHA256: 2c8ace646c8755643d941410cd5cbc82fcb7b78d4fc751e4fa0aac7dcd4a60d7
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.6.0~beta.1
Architecture: arm64
Essential: no
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 1024
Depends: zenohd (=0.6.0~beta.1), zenoh-plugin-rest (=0.6.0~beta.1), zenoh-plugin-storage-manager (=0.6.0~beta.1)
Filename: 0.6.0-beta.1/zenoh_0.6.0~beta.1_arm64.deb
Size: 836
MD5sum: 5fdf03c0eb357acc330ac51f7e56e656
SHA1: 01a5ddbe7ebc73f3abe2087f17a419e792b18201
SHA256: 04154c6de345e5df219a6bafe7df155b1caaff6718d565fe4acb6e87f773106a
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.6.0~beta.1
Architecture: armhf
Essential: no
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 1024
Depends: zenohd (=0.6.0~beta.1), zenoh-plugin-rest (=0.6.0~beta.1), zenoh-plugin-storage-manager (=0.6.0~beta.1)
Filename: 0.6.0-beta.1/zenoh_0.6.0~beta.1_armhf.deb
Size: 832
MD5sum: 2b3fa85a9fb1288941fe0fab786ed201
SHA1: f38e101225efdb2626f46d96ad6a7975e7272689
SHA256: 00c433bccf4b5e024a21c82d97ed4228dfad1041330f1cada8faaa86878413a2
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.6.0~beta.1
Architecture: armel
Essential: no
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 1024
Depends: zenohd (=0.6.0~beta.1), zenoh-plugin-rest (=0.6.0~beta.1), zenoh-plugin-storage-manager (=0.6.0~beta.1)
Filename: 0.6.0-beta.1/zenoh_0.6.0~beta.1_armel.deb
Size: 832
MD5sum: dae34bccc287d47b94eacd53051c08c4
SHA1: 4862692a34b61c024e3dc63f81b07965bf0d6a95
SHA256: 8135af4d6e46a6c4f7ca4a21b134c5863d632716c5194cfc569e6520b1f67dee
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.6.0~beta.1
Architecture: armhf
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 5769
Depends: zenoh-plugin-storage-manager (=0.6.0~beta.1)
Filename: 0.6.0-beta.1/zenoh-backend-filesystem_0.6.0~beta.1_armhf.deb
Size: 2301044
MD5sum: 38a6609b97d581dff9251411ce80b36e
SHA1: f41fe73286458ffe93dc97927190c40ba8219e09
SHA256: 811a4becbbc6a91a824abb1a3184b1dc4b0d120965b6710e5c74c497dfe6e750
Section: net
Priority: optional
Description: [generated from Rust crate zenoh_backend_filesystem]
Package: zenoh-backend-filesystem
Version: 0.6.0~beta.1
Architecture: amd64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 9058
Depends: zenoh-plugin-storage-manager (=0.6.0~beta.1)
Filename: 0.6.0-beta.1/zenoh-backend-filesystem_0.6.0~beta.1_amd64.deb
Size: 2735212
MD5sum: 25448190d975002b93bc98d0c8f12dc2
SHA1: feb4a010ac5c13e40eeaf951244582c6c5b44140
SHA256: 054a1e34d8d71b356576513dafb0b07dd9019f6b299b01fb6b287694a8b2f5ed
Section: net
Priority: optional
Description: [generated from Rust crate zenoh_backend_filesystem]
Package: zenoh-backend-filesystem
Version: 0.6.0~beta.1
Architecture: armel
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 7313
Depends: zenoh-plugin-storage-manager (=0.6.0~beta.1)
Filename: 0.6.0-beta.1/zenoh-backend-filesystem_0.6.0~beta.1_armel.deb
Size: 2231512
MD5sum: b9db55406e1b36a6dcfd7e5c240250fb
SHA1: 54aca06fc06e8b03fe13f09fe07ccb0c57b8ff74
SHA256: 5b4f90f88c3fe4c3adf97fa2bc30e6f9d089102012be6b955f827a9d43bf49b0
Section: net
Priority: optional
Description: [generated from Rust crate zenoh_backend_filesystem]
Package: zenoh-backend-filesystem
Version: 0.6.0~beta.1
Architecture: arm64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 7739
Depends: zenoh-plugin-storage-manager (=0.6.0~beta.1)
Filename: 0.6.0-beta.1/zenoh-backend-filesystem_0.6.0~beta.1_arm64.deb
Size: 2260956
MD5sum: a8bb144ae490386bff981d87a0797a97
SHA1: a0269a96fc0d1f52db5bf17857608ab79856ef8b
SHA256: bdd26b59cadc9bf095339801a2a5c3e59b1c16a0062817cb235a7c99af1643ed
Section: net
Priority: optional
Description: [generated from Rust crate zenoh_backend_filesystem]
Package: zenoh-backend-influxdb
Version: 0.6.0~beta.1
Architecture: arm64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 4353
Depends: zenoh-plugin-storage-manager (=0.6.0~beta.1)
Filename: 0.6.0-beta.1/zenoh-backend-influxdb_0.6.0~beta.1_arm64.deb
Size: 1320300
MD5sum: db218403921d36648aa8692d1e6b558c
SHA1: 7087ce8a1b27caa5d52cf3b66bf202329420d9b2
SHA256: b368bf0efaf7f12bdc01c5d06644e9e53b362496ce154b130a0892d1631657b5
Section: net
Priority: optional
Description: [generated from Rust crate zenoh_backend_influxdb]
Package: zenoh-backend-influxdb
Version: 0.6.0~beta.1
Architecture: armhf
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 3884
Depends: zenoh-plugin-storage-manager (=0.6.0~beta.1)
Filename: 0.6.0-beta.1/zenoh-backend-influxdb_0.6.0~beta.1_armhf.deb
Size: 1154164
MD5sum: 3e62894e18c222ec902aa95a6d390833
SHA1: f8f707cbfbe6972e1e9d0db1d4c66a4196931331
SHA256: fd74183b30113bfb61f5eab2f2ffc58ebbbfd15591e13be532d9658ca0f82f4d
Section: net
Priority: optional
Description: [generated from Rust crate zenoh_backend_influxdb]
Package: zenoh-backend-influxdb
Version: 0.6.0~beta.1
Architecture: amd64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 4921
Depends: zenoh-plugin-storage-manager (=0.6.0~beta.1)
Filename: 0.6.0-beta.1/zenoh-backend-influxdb_0.6.0~beta.1_amd64.deb
Size: 1512484
MD5sum: 1351cafb3426fbd8a2ae72dd770285fc
SHA1: 3f6700a018089b08366663c3e65a6bae7375f5c7
SHA256: 8917624686fd090226f76919c51baa95a0ff5185c7b14b7cc1a493d059681df4
Section: net
Priority: optional
Description: [generated from Rust crate zenoh_backend_influxdb]
Package: zenoh-backend-influxdb
Version: 0.6.0~beta.1
Architecture: armel
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 3976
Depends: zenoh-plugin-storage-manager (=0.6.0~beta.1)
Filename: 0.6.0-beta.1/zenoh-backend-influxdb_0.6.0~beta.1_armel.deb
Size: 1153228
MD5sum: 106d8b767bc4f28087867b5898e632d4
SHA1: 82dc129c6f45f9a917fcbdf3c87634b7be6b361e
SHA256: 503370682524b352a968147e01918bc06e80dbd624c12581ea30656c9801817f
Section: net
Priority: optional
Description: [generated from Rust crate zenoh_backend_influxdb]
Package: zenoh-backend-rocksdb
Version: 0.6.0~beta.1
Architecture: arm64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 7595
Depends: zenoh-plugin-storage-manager (=0.6.0~beta.1)
Filename: 0.6.0-beta.1/zenoh-backend-rocksdb_0.6.0~beta.1_arm64.deb
Size: 2239168
MD5sum: 8aa09fe69cec01a6f72f652f62b722bf
SHA1: cc48742050e962249f9c155b2e487cb8a69b9e88
SHA256: 954c1f148d611785de953d52737e6459e868593c188c771a4368afc40d649a52
Section: net
Priority: optional
Description: [generated from Rust crate zenoh_backend_rocksdb]
Package: zenoh-backend-rocksdb
Version: 0.6.0~beta.1
Architecture: amd64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 8934
Depends: zenoh-plugin-storage-manager (=0.6.0~beta.1)
Filename: 0.6.0-beta.1/zenoh-backend-rocksdb_0.6.0~beta.1_amd64.deb
Size: 2707936
MD5sum: 1644f2fb9f2c28a657e012d82e6e3774
SHA1: 11915a54b5c06f2d0e8887eeaa689436faec5a8a
SHA256: 54082c8b3a313e1d4b2223f934138909f669c22385f138c9d1691907875f23e4
Section: net
Priority: optional
Description: [generated from Rust crate zenoh_backend_rocksdb]
Package: zenoh-backend-rocksdb
Version: 0.6.0~beta.1
Architecture: armel
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 7253
Depends: zenoh-plugin-storage-manager (=0.6.0~beta.1)
Filename: 0.6.0-beta.1/zenoh-backend-rocksdb_0.6.0~beta.1_armel.deb
Size: 2211356
MD5sum: 593e0ab2fa00663c07a750dc92c0b54c
SHA1: 015d4e6dacb5fbaf7748ac1419d1081320bb1795
SHA256: 7c0dbb2bf6f2f8c081b631e8905b48dc6e773d401310497a4a76cc85b321b983
Section: net
Priority: optional
Description: [generated from Rust crate zenoh_backend_rocksdb]
Package: zenoh-backend-rocksdb
Version: 0.6.0~beta.1
Architecture: armhf
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 5677
Depends: zenoh-plugin-storage-manager (=0.6.0~beta.1)
Filename: 0.6.0-beta.1/zenoh-backend-rocksdb_0.6.0~beta.1_armhf.deb
Size: 2278804
MD5sum: f26f77ccb71edc350cb93af640bcb31f
SHA1: 013c775a860dba9f6824e987ef7f79c61a6f91bd
SHA256: 0dffe496e316ba23507013f74331d221b85f920ba037e10fd5020be3b8c6f565
Section: net
Priority: optional
Description: [generated from Rust crate zenoh_backend_rocksdb]
Package: zenoh-bridge-dds
Version: 0.6.0~beta.1
Architecture: armel
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 8442
Filename: 0.6.0-beta.1/zenoh-bridge-dds_0.6.0~beta.1_armel.deb
Size: 2609164
MD5sum: 72c56acd0881a63475642c10473a0929
SHA1: b684dafe4b8258f0f9c53368bd9457a81314bd08
SHA256: ae7a3fbf578b285a10603e1a099b9e03bb23dbca5d05a0976e0a24469985aecd
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-bridge-dds
Version: 0.6.0~beta.1
Architecture: arm64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 8080
Filename: 0.6.0-beta.1/zenoh-bridge-dds_0.6.0~beta.1_arm64.deb
Size: 2620912
MD5sum: 417f16fac83de2f4b8f9679f7733f8b2
SHA1: 193c45119a7830e941e5ed308007954cfb9ac2fc
SHA256: 3fd963be98ed148122617b0547e4ed69bcbc9aac81bf0b0688caf12344348938
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-bridge-dds
Version: 0.6.0~beta.1
Architecture: amd64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 9364
Depends: libc6 (>= 2.29)
Filename: 0.6.0-beta.1/zenoh-bridge-dds_0.6.0~beta.1_amd64.deb
Size: 2945608
MD5sum: 6cd39628c998961524c8645c5be7bc0b
SHA1: cfedccd53855bddc086dbeb284f3cdc338d27960
SHA256: 3b2673fd39d54534ccb5d69aa786f2fa0982c4080a30b4f3f1d28df5bd6269bb
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-bridge-dds
Version: 0.6.0~beta.1
Architecture: armhf
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 8058
Filename: 0.6.0-beta.1/zenoh-bridge-dds_0.6.0~beta.1_armhf.deb
Size: 2629856
MD5sum: 4af35f65bfa08e45775765ab6596066d
SHA1: 7d9f6ce721f35b60b3f327e0b070a023f3e0bd74
SHA256: 3b1b9c72efa97c105798f1d960cd9ae935c3c1324790c6ac6620c4aebcbb2cd5
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.6.0~beta.1
Architecture: amd64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 3902
Depends: zenohd (=0.6.0~beta.1)
Filename: 0.6.0-beta.1/zenoh-plugin-dds_0.6.0~beta.1_amd64.deb
Size: 1147916
MD5sum: 7eb86db8702a3c4dc5efe2932e70d55f
SHA1: 6b9e799607bfebb3340ac68979bcde847bd7af01
SHA256: 5a00ca0a432a5317b88c034962917fc5cfcc3a84bce3ed17496b1c183d5c6ee4
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.6.0~beta.1
Architecture: armel
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 3465
Depends: zenohd (=0.6.0~beta.1)
Filename: 0.6.0-beta.1/zenoh-plugin-dds_0.6.0~beta.1_armel.deb
Size: 1017568
MD5sum: 583d886589ea3808218dd74fd752636d
SHA1: cc322fea56b7be3aa82fd47e8523c8f3596fc281
SHA256: b617853714cee389cc50a55291451bede3bfe7b31829207cb3d1d6ba8a056e11
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.6.0~beta.1
Architecture: armhf
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 3213
Depends: zenohd (=0.6.0~beta.1)
Filename: 0.6.0-beta.1/zenoh-plugin-dds_0.6.0~beta.1_armhf.deb
Size: 1028208
MD5sum: 52cf327b432baf37ae5f1452cd72c618
SHA1: cfdbf4700ef67ddeae2f66724ea6d7596aacb750
SHA256: 6b538df72ab7dd7f75e5ca6109bf0a000a8d904f98dac2f8d92e88a682fbec06
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.6.0~beta.1
Architecture: arm64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 3442
Depends: zenohd (=0.6.0~beta.1)
Filename: 0.6.0-beta.1/zenoh-plugin-dds_0.6.0~beta.1_arm64.deb
Size: 987312
MD5sum: 24bee50067e718df3c8b3642e6f8c91e
SHA1: 611147db2b67387a4a06dc3364c6da459651984e
SHA256: 31d15cf7b7e129ffda32a742de49c7ab8e412e9899ddc8ff5d46026797b5fcd8
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-rest
Version: 0.6.0~beta.1
Architecture: arm64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 2910
Depends: zenohd (=0.6.0~beta.1)
Filename: 0.6.0-beta.1/zenoh-plugin-rest_0.6.0~beta.1_arm64.deb
Size: 804908
MD5sum: 5c9f2de75135855be3a4af74ad19e24d
SHA1: e809ca0b6591bb19ccffcc4f606863020f70413f
SHA256: 4202a3a7fa635d373dd892f3b44c570d6ee743512582dba4823da5041b0e2e99
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.6.0~beta.1
Architecture: armel
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 2881
Depends: zenohd (=0.6.0~beta.1)
Filename: 0.6.0-beta.1/zenoh-plugin-rest_0.6.0~beta.1_armel.deb
Size: 821144
MD5sum: 1241287a6bde35e7d2dad8e5fae6ad13
SHA1: 06e7ca057231b2e3176d4942e68a3e8d9493cc07
SHA256: 8464b7c326d7425ffb1376745645a85267acc24f5ca142414288c63287066799
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.6.0~beta.1
Architecture: armhf
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 2821
Depends: zenohd (=0.6.0~beta.1)
Filename: 0.6.0-beta.1/zenoh-plugin-rest_0.6.0~beta.1_armhf.deb
Size: 814708
MD5sum: 2864deeb24cbc08798acea55310f7189
SHA1: fc42303690cd3b01bf1d7385ad2a8a1cf96175de
SHA256: 224d34de5a651a51272461357838b7db8813f26abb5f32e8434456360aaffcec
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.6.0~beta.1
Architecture: amd64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 3274
Depends: zenohd (=0.6.0~beta.1)
Filename: 0.6.0-beta.1/zenoh-plugin-rest_0.6.0~beta.1_amd64.deb
Size: 924176
MD5sum: ae21200e814a3b24f57e47d8f073cff6
SHA1: 2cdf5061098c9b636d91768373c90250f327435c
SHA256: 73bf0f984ffb23978c784017378a663465e2ac4503c9d35dab1ffb890f0f4ee2
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.6.0~beta.1
Architecture: armhf
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 2621
Depends: zenohd (=0.6.0~beta.1)
Filename: 0.6.0-beta.1/zenoh-plugin-storage-manager_0.6.0~beta.1_armhf.deb
Size: 815012
MD5sum: 664945ac81cda99dbffbfedbd18adf88
SHA1: cc53281aef407efc36f641857dd675cee3811013
SHA256: 4f2cf38f891f713170c9a3c90362a1890639fe36a1e76b29a46d285c1f73ee3f
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.6.0~beta.1
Architecture: arm64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 2626
Depends: zenohd (=0.6.0~beta.1)
Filename: 0.6.0-beta.1/zenoh-plugin-storage-manager_0.6.0~beta.1_arm64.deb
Size: 771440
MD5sum: c12c5694004fa55dd0fa0deb8308ec54
SHA1: 97d6c61febafe9a4c2a3092caf1c1dc02f39bd4a
SHA256: d5374c5177ce48758c96446e44e8c64e24a344b01d828e5a35f4afd1cecb09b0
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.6.0~beta.1
Architecture: armel
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 2677
Depends: zenohd (=0.6.0~beta.1)
Filename: 0.6.0-beta.1/zenoh-plugin-storage-manager_0.6.0~beta.1_armel.deb
Size: 818992
MD5sum: d3beae0647c55ff212a87fa02245a9b9
SHA1: 884e9b0827963fd5950ee8589d4a191bb98b0e6e
SHA256: 14cdc33e2e49db681da5cd1feed1eaccf1bac05726b26a150a31941fa43742b1
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.6.0~beta.1
Architecture: amd64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 2982
Depends: zenohd (=0.6.0~beta.1)
Filename: 0.6.0-beta.1/zenoh-plugin-storage-manager_0.6.0~beta.1_amd64.deb
Size: 887000
MD5sum: a4d4b54fc4bc8027496772e1a3989502
SHA1: ce4025c721273d261c23fe26ef295ba0f0571916
SHA256: b7eb85e4707c48deec02504690d07f46fac4e024e40f47e33e0bda53ee19be94
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.6.0~beta.1
Architecture: armel
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 3904
Depends: zenohd (=0.6.0~beta.1)
Filename: 0.6.0-beta.1/zenoh-plugin-webserver_0.6.0~beta.1_armel.deb
Size: 986596
MD5sum: af2a7d86af3b2d7217ef7478dbc7a1b8
SHA1: a10f839f55f12b86c4c8031d671f876910a271e4
SHA256: ee751bdc9b0a6288a0cc13a94293125951dee2ec109d24b733fd9e2765e965d9
Section: net
Priority: optional
Description: [generated from Rust crate zenoh_plugin_webserver]
Package: zenoh-plugin-webserver
Version: 0.6.0~beta.1
Architecture: armhf
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 3808
Depends: zenohd (=0.6.0~beta.1)
Filename: 0.6.0-beta.1/zenoh-plugin-webserver_0.6.0~beta.1_armhf.deb
Size: 978292
MD5sum: 46a80d3b881a137d45965ff40b797879
SHA1: 356b8036ad6d9ee1fa2cae338ffdeecb15545f42
SHA256: fed5b6494249331a1f77832248aac922a0bdde51c1e82ea6b0cc89e1e9ab8868
Section: net
Priority: optional
Description: [generated from Rust crate zenoh_plugin_webserver]
Package: zenoh-plugin-webserver
Version: 0.6.0~beta.1
Architecture: amd64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 4497
Depends: zenohd (=0.6.0~beta.1)
Filename: 0.6.0-beta.1/zenoh-plugin-webserver_0.6.0~beta.1_amd64.deb
Size: 1175408
MD5sum: 81be67260f195b1999c946574fc5d391
SHA1: f151908e3480da66182f925441fb97a177ee1935
SHA256: 0452cf06c1d8df53dbec0137a75659936e3e5deaf4ca5faf6cfe0d20b157cee2
Section: net
Priority: optional
Description: [generated from Rust crate zenoh_plugin_webserver]
Package: zenoh-plugin-webserver
Version: 0.6.0~beta.1
Architecture: arm64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 4145
Depends: zenohd (=0.6.0~beta.1)
Filename: 0.6.0-beta.1/zenoh-plugin-webserver_0.6.0~beta.1_arm64.deb
Size: 1032684
MD5sum: 0ec670579caa6d01958ebc1e9727a501
SHA1: 2ee6abbdd23dbc8906869ec26152d21ce9b358d3
SHA256: 387806bf244a1eea90d162f6501d51aeb1675969dfcf1aca18d062a04d4cb418
Section: net
Priority: optional
Description: [generated from Rust crate zenoh_plugin_webserver]
Package: zenohd
Version: 0.6.0~beta.1
Architecture: armhf
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 6313
Depends: libc6:armhf (>= 2.31)
Filename: 0.6.0-beta.1/zenohd_0.6.0~beta.1_armhf.deb
Size: 1981388
MD5sum: dad6f60946e1f033aa736ab73df6b48e
SHA1: ca65ffd8bfc75931c0621965cf3adea42d1cfb74
SHA256: 30698a7f044bf28033ed75c1ae789ca944bc3a171a9be4cb636cf9b1cc911aaf
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/vSDSpqnbkm)
[](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.
.
Eclipse zenoh (pronounce _/zeno/_) unifies data in motion, data in-use, 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.
.
-------------------------------
## How to install and test it
.
See our _"Getting started"_ tour starting with the [zenoh key
concepts](https://zenoh.io/docs/getting-started/key-concepts/).
.
-------------------------------
## How to build it
.
Install [Cargo and
Rust](https://doc.rust-lang.org/cargo/getting-started/installation.html). Zenoh
can be succesfully compiled with Rust stable (>= 1.5.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
```
.
The zenoh 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/0.0.0.0: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
(`0.0.0.0`) 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.6.0~beta.1
Architecture: armel
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 6481
Depends: libc6:armel (>= 2.31)
Filename: 0.6.0-beta.1/zenohd_0.6.0~beta.1_armel.deb
Size: 1980852
MD5sum: 129bfadb708931c7e45dee986d8c63da
SHA1: c50bf201118edd8d4ed4c0d9c964cbc5c2fa5a08
SHA256: 2a81cc0c82452b9ab7c989bbe850c9a705c4a555cd36cbcae7c1f6022f5eb35e
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/vSDSpqnbkm)
[](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.
.
Eclipse zenoh (pronounce _/zeno/_) unifies data in motion, data in-use, 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.
.
-------------------------------
## How to install and test it
.
See our _"Getting started"_ tour starting with the [zenoh key
concepts](https://zenoh.io/docs/getting-started/key-concepts/).
.
-------------------------------
## How to build it
.
Install [Cargo and
Rust](https://doc.rust-lang.org/cargo/getting-started/installation.html). Zenoh
can be succesfully compiled with Rust stable (>= 1.5.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
```
.
The zenoh 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/0.0.0.0: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
(`0.0.0.0`) 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.6.0~beta.1
Architecture: amd64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 7310
Depends: libc6 (>= 2.28)
Filename: 0.6.0-beta.1/zenohd_0.6.0~beta.1_amd64.deb
Size: 2262512
MD5sum: 1bf7fd54a3413dac35e735d18c1c0da7
SHA1: e22a33c450b59ccc6e8de02147716eb0b7ccdf43
SHA256: de59cbf776704ed07d6e41217fb387aec46125406a7d905c056ba09d854f461b
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/vSDSpqnbkm)
[](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.
.
Eclipse zenoh (pronounce _/zeno/_) unifies data in motion, data in-use, 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.
.
-------------------------------
## How to install and test it
.
See our _"Getting started"_ tour starting with the [zenoh key
concepts](https://zenoh.io/docs/getting-started/key-concepts/).
.
-------------------------------
## How to build it
.
Install [Cargo and
Rust](https://doc.rust-lang.org/cargo/getting-started/installation.html). Zenoh
can be succesfully compiled with Rust stable (>= 1.5.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
```
.
The zenoh 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/0.0.0.0: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
(`0.0.0.0`) 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.6.0~beta.1
Architecture: arm64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 6222
Depends: libc6:arm64 (>= 2.31)
Filename: 0.6.0-beta.1/zenohd_0.6.0~beta.1_arm64.deb
Size: 2007804
MD5sum: 283dbc97623c337b534dfd81c3565434
SHA1: 9a1bc554cd5dc077ba303cb58cd26547d8fbf35d
SHA256: 64cc8a67b49e72e6751b220b3ce6c832108a3a1b56d9c7842e599b38899d109b
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/vSDSpqnbkm)
[](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.
.
Eclipse zenoh (pronounce _/zeno/_) unifies data in motion, data in-use, 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.
.
-------------------------------
## How to install and test it
.
See our _"Getting started"_ tour starting with the [zenoh key
concepts](https://zenoh.io/docs/getting-started/key-concepts/).
.
-------------------------------
## How to build it
.
Install [Cargo and
Rust](https://doc.rust-lang.org/cargo/getting-started/installation.html). Zenoh
can be succesfully compiled with Rust stable (>= 1.5.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
```
.
The zenoh 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/0.0.0.0: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
(`0.0.0.0`) 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