Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What's the plan to release 1.0 version #5

Open
lygstate opened this issue Nov 14, 2018 · 8 comments
Open

What's the plan to release 1.0 version #5

lygstate opened this issue Nov 14, 2018 · 8 comments

Comments

@lygstate
Copy link

No description provided.

@kydos
Copy link
Contributor

kydos commented Nov 14, 2018

@lygstate, we have been building a pretty neat brokering system for the zenoh( http://zenoh.io) protocol -- see the information on http://github.com/atolab/zenoh-python on how to give it a run. The version v1.0 of zhe will be released once we'll be sufficiently happy with having a v1.0 for the whole infrastructure. You may wonder why... In essence we tie the major version of all the different elements in the zenoh ecosystem to the protocol version. This guarantees that anything sharing the same major version will interoperate.

If your questions concerns the maturity of the zhe code base, you could consider it as a beta status.

A+

@lygstate
Copy link
Author

so zenoh-python are the broker?

@kydos
Copy link
Contributor

kydos commented Nov 16, 2018

No, that's only the python client API. The brokering system is not currently open source. However you can use it through demo.zenoh.io. If you are interested in specific investigation do not hesitate to contact me at angelo.corsaro@adlinktech.com

@lygstate
Copy link
Author

@kydos Would the brokering system be open source, or would be close source permanantly?

@kydos
Copy link
Contributor

kydos commented Nov 16, 2018

@lygstate, it will be open sourced in the near future. I think we'll be in the position to share the plans for zenoh in a couple of months. I'd be curious to know what'd your like to use it for, we could provide you with some docker alpine images. In any case we are always happy to get feedback from users.

@lygstate
Copy link
Author

@kydos I want to use zhe in VxWorks for communication with PC.
DDS is too big for VxWorks even thoug it's realtime nature.
Does zhe's realtime performance can match DDS's performance?
I don't like DDS's IDL things(from CORBA), I would use zhe to transfering Variable Length Array( such as JSON)

@kydos
Copy link
Contributor

kydos commented Nov 16, 2018

@lygstate that makes sense. In all of our performance evaluation zenoh runs faster and with lower jitter than DDS. The difference is bigger on smaller hardware. Thus, with zenoh you can typically match or exceed DDS performances. Concerning your deployment you can use zhe as either a C-Client or for peer-to-peer communication. If you want to try the broker you can checkout the alpine docker instance available at https://hub.docker.com/r/kydos/zenoh/

To play around with the broker I suggest you use the python API available at http://github.com/atolab/zenoh-python

Let me know if you have any issues.

@kydos

@seimonw
Copy link

seimonw commented Jun 7, 2019

Hi @kydos, is there any further news on the zenoh v1.0 developments that you can share?
Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants