News for hackers. Stuff that matters.

A comment on Dropbox’s Exodus from the Amazon Cloud. Parent comment

Re:Dropbox’s Exodus from the Amazon Cloud by jabl on Monday March 14, 2016 @05:09PM (#11285597)
How do you do network io with rust? Thread-per-connection, non-blocking (using mio or?), or something else?
[ Parent | on HN ]
Re:Dropbox’s Exodus from the Amazon Cloud by jamwt on Monday March 14, 2016 @05:29PM (#11285718)
We have an in-house futures-based framework (inspired by Finagle) built on mio (non-blocking libevent like thing for rust). All I/O is async, but application work is often done on thread pools. Those threads are freed as soon as possible, though, so that I/O streams can be handled purely by "the reactor", and we keep the pools as small as possible.
[ Parent | on HN ]
Re:Dropbox’s Exodus from the Amazon Cloud by windlep on Monday March 14, 2016 @07:27PM (#11286360)
Any plans to open-source the futures-based Rust framework? :)
[ Parent | on HN ]
Re:Dropbox’s Exodus from the Amazon Cloud by dikaiosune on Monday March 14, 2016 @07:37PM (#11286403)
From a parallel conversation[0] on the Rust subreddit:

>Are you going to open source anything?

>Probably. We have an in-house futures-based I/O framework. We're going to collaborate with the rust team and Carl Lerche to see if there's something there we can clean up and contribute.

[0]: https://www.reddit.com/r/rust/comments/4adabk/the_epic_story...

[ Parent | on HN ]