Rails is not event-based. An evented systems can have an n:m relation between workers and clients.
> I may have misunderstood what we were getting in Rails 4, then.
Yeah, or I did. As far as i understood, Rails 4 just adds streaming responses: the client starts getting bytes as soon as you start generating them (by calling `response.write` or whatever). That's not evented, that's just writing to the response stream, you can do that in CGI if you want.
Comments
> So even though it's event-based
Rails is not event-based. An evented systems can have an n:m relation between workers and clients.
> I may have misunderstood what we were getting in Rails 4, then.
Yeah, or I did. As far as i understood, Rails 4 just adds streaming responses: the client starts getting bytes as soon as you start generating them (by calling `response.write` or whatever). That's not evented, that's just writing to the response stream, you can do that in CGI if you want.