I'd like to emphasize that Rust's standard libraries are all somewhat haphazard to various degrees, so I wouldn't presume that anything that is currently possible or impossible via the libraries implies any sort of overarching design philosophy. Though considering how many people seem eager to build servers in Rust, networking is probably an area that could use some refinement sooner rather than later.
On Wed, Oct 24, 2012 at 3:41 AM, [email protected] <[email protected]>wrote: > Hi, > I'm starting with rust, although I've been looking inside for a while its > the first time I try writing real rust code. > So, I pulled from master yesterday and wrote this simple server > http://pastebin.com/MMiNpXYG > > No tasks, no concurrency, a single-threaded, single-tasked server, that to > my eyes should be able to handle one client after another, however, I seem > to be unable to see any other client than the first one in the server, > netcat does not complain but listen.rs does not see the new client. > Am I doing anything wrong? > > AFAIK, rust is not going to support traditional socket handling, > everything is going to go over libuv, is this statement correct? > > Thanks > > -- > Arkaitz > > _______________________________________________ > Rust-dev mailing list > [email protected] > https://mail.mozilla.org/listinfo/rust-dev > >
_______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
