Hi, On Wed, Nov 16, 2016 at 07:48:36PM +0100, Eddy Bruel wrote:
> To make IPC channels usable with Tokio, we'd have to take whatever low > level IO primitive IPC channels use under the hood, and then reimplement > the same logic that the existing IPC channels implement on top of this, but > using a streams based API (by streams, I mean the streams from the > futures-rs, crate). > > I'm not quite sure how much work this would be, since I don't know how > complex ipc channels are under the hood. The low-level I/O in some of the platform back-ends in ipc-channel is quite intricate -- and might change in incompatible ways at any time. I don't think it's a good idea to try reimplementing it. Rather, we should try to reuse as much of the existing low-level code as we can, while creating an alternative API entry point. My *intuition* is that this should be quite doable -- though of course I might be wrong... Especially since I'm not really familiar with Tokio yet, beyond having some very rough idea of what it does. -antrik- _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
