Nanomsg looks interesting and I'll take a closer look. But I'm interested in a pure rust implementation of async messaging because I'd like to create an embedded OS using rust and not use C if possible.
I been thinking about the problem and one of the questions I have is how to transfer ownership of a pointer from one entity to another. Not borrow but actually transfer ownership. So if I "allocated" a Message in one entity then send it to another I want the receiver to "free" the Message. Does the rust ownership model allow ownership to be transferred? -- Wink On Sep 29, 2014 3:04 AM, "Heiko Braun" <ike.br...@googlemail.com> wrote: > I havn't looked at it in detail, but nanomsg [1] seems to cover these > requirements. There's a rust binding [2] available too. > > Regards, Heiko > > [1] http://nanomsg.org > [2] https://github.com/thehydroimpulse/nanomsg.rs > > > > On 28 Sep 2014, at 03:54, Wink Saville <w...@saville.com> wrote: > > I'd like to have one API which would allow sending/receiving messages > asynchronously, safely and efficiently over any transport and should work > for components that run in the same thread, different threads, different > processes or between devices which might be connected via any arbitrary > hardware. > > Has any such API been developed? > > -- wink > _______________________________________________ > Rust-dev mailing list > Rust-dev@mozilla.org > https://mail.mozilla.org/listinfo/rust-dev > > >
_______________________________________________ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
