From: Tony Arcieri Date: 2008-02-16T10:14:23+09:00 Subject: Re: eventmachine and rev ------=_Part_3152_4925091.1203124460444 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Fri, Feb 15, 2008 at 5:42 PM, Roger Pack wrote: > Can it buffer incoming I/O? > The actual C buffering code has support for buffering incoming I/O with Rev::Buffer#read_from(io). However, Rev just dispatches any incoming data it reads as it's read through the on_read callback. However, read buffering is performed by Revactor, which provides an imperative, blocking read API, which works just like IO#read Which features? > Off the top of my head, EventMachine has many protocol adapters including SMTP and a (separately bundled) evented HTTP server with an associated REST framework, not to mention Evented Mongrel and Thin. It also implements the Deferrable pattern for performing blocking calls alongside the event loop. I'm sure there's many more things I'm omitting here. Rev bundles an asynchronous DNS client which it uses internally for all DNS resolution, as well as an HTTP client. Right now there are no HTTP server bindings for it. Revactor allows you to run Mongrel on top of Rev using Actors for concurrency. -- Tony Arcieri ClickCaster, Inc. tony@clickcaster.com ------=_Part_3152_4925091.1203124460444--