Initial implementation of up-streamer-rust - UTransport Non-thread-safe version
#7
Conversation
|
Paging @sophokles73, @AnotherDaniel, @evshary for your kind guidance 🤗 |
|
Realizing I forgot to swap out the |
Finished with this now |
…nc-broadcast so each Receiver gets what's sent by any Sender.
| authors = [ | ||
| "Pete LeVasseur <[email protected]>", | ||
| ] |
There was a problem hiding this comment.
Is this supposed to become an exhaustive list of contributors? The Eclipse Foundation considers maintaining such lists obsolete because everybody can derive it from the Git log. This might have some value for pointing out a prime contact for the project, though, if that is what you had intended to do :-)
There was a problem hiding this comment.
Huh. I wonder -- should we have one or two primary points of contact for each of the projects that we put in here?
I get what you mean about keeping track of all contributors to be not needed.
| ] | ||
|
|
||
| [workspace.package] | ||
| rust-version = "1.66.1" |
There was a problem hiding this comment.
is this aligned (and verified) with all of your upstream dependencies?
There was a problem hiding this comment.
Can check.
What's the best way to do this? Checking dependencies' Cargo.toml manually?
…r publishes and one for request, response, and notifications
…ete_forwarding_rule() can forward
… we receive it over the UTransport and then put in an Arc<UMessage> so when we're passing these around between channels it's only as big as a fat pointer, not as big as the entire UMessage.
PLeVasseur
force-pushed
the
feature/initial-pluggable-ustreamer
branch
from
9e8bbb7
to
cf2f9ab
Compare
PLeVasseur
changed the title
up-streamer-rustup-streamer-rust - Non-thread-safe version
PLeVasseur
changed the title
up-streamer-rust - Non-thread-safe versionup-streamer-rust - UTransport Non-thread-safe version
|
Closing in favor of #8 Going to move unresolved comments over |
Hey there 👋
Based on @stevenhartley's stellar design, I reworked the in-progress first PR I had.
Looking for any feedback you may have 🙂
I suppose this would be to address #3