I am considering authoring a webserver (think nginx, apache, cowboy,
etc) in Rust. From a user point of view, mapping tasks (green) to web
requests makes the most sense as the tasks could be long running,
perform their own I/O, sessions, or what have you. It would also allow
the user to do
the current
workload.
-- Matthieu
On Sat, Apr 12, 2014 at 11:04 AM, Jeremy Ong jeremyc...@gmail.com wrote:
I am considering authoring a webserver (think nginx, apache, cowboy,
etc) in Rust. From a user point of view, mapping tasks (green) to web
requests makes the most sense as the tasks could
I have long touted Bundler as one of the greatest tools for package
management currently in existence and have missed its presence when
working in C++ and many other languages. This is a very welcome
development indeed for the Rust ecosystem and I'm excited to see what
becomes of it.
On Mon, Mar
Rubygems is, in my opinion, one of the best examples of package managers
for a programming language out there. I don't use ruby currently but I
recall liking it much more than the competition, at least as of a few years
ago. In no particular order, it features:
- central repository
- optionally
I'm somewhat new to the Rust dev scene. Would anybody care to summarize
roughly what the deficiencies are in the existing system in the interest of
forward progress? It may help seed the discussion for the next effort as
well.
On Mon, Jan 27, 2014 at 6:05 PM, Steve Klabnik
Rust should be providing the building blocks for a concurrency pattern
determined by the needs of the application. I don't think it should
push a specific design, as there are many ways of doing this with
their own merits.
There is a spectrum of flexibility and safety. I'll be honest, if
