-
Notifications
You must be signed in to change notification settings - Fork 13
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
Initial implementation of up-linux-streamer #16
Initial implementation of up-linux-streamer #16
Conversation
1151b40
to
10b6358
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like currently the streamer is limited to using the Zenoh and the VSomeIP transport only. I would suggest to start decoupling from the concrete transport ASAP because this will make apparent any required changes to the transports very quickly ...
The underlying pluggable library (up-streamer) is decoupled and independent. The binary which does the work of plugging in concrete transports does need to depend on the concrete implementations, right? I plan to peg those to a tagged version for Zenoh and SOME/IP in the Cargo.toml to prevent main from breaking. Does that plan make sense? Or would it make more sense to leave pointing to main and then enable a nightly CI to check for breaking changes in transports & up-rust? |
FMPOV you should guard support for specific transports using Rust features. When building the application, users can then easily enable only those transport(s) that they need. |
896433a
to
c5f58b6
Compare
This makes some sense. I'll have to think about this a bit. Opened an issue here: #32 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
* Add up-linux-streamer * Include ability to pass config file * Include default config file with comment explaining * Ability to pass --no-default-features to bring own vsomeip shared libraries * Add examples and documentation on how to use them with up-linux-streamer * These use the HelloRequest and HelloResponse COVESA uService helloworld .proto objects * mE_client <=> uE_service * uE_client <=> mE_service * Update CI to test both bundled and unbundled vsomeip library configurations Implements [#4], [#5]
c5f58b6
to
4716a05
Compare
Outline
Basic showcase of how a up-linux-streamer can work to bridge the RPC flow between mE and uE between SOME/IP <--> Zenoh
TODO
Covers #4, #5