> On Thu, Jul 19, 2012 at 9:22 AM, Roberto De Ioris <[email protected]> > wrote: >> The concept is pretty simple (and already used by other projects like >> Mongrel2 ot zerogw), the server parses the http request and build a >> series >> of zeromq messages forwarded to one or more backend nodes. > > _very_ intresting! > > can you expand a little on what makes this different from Mongrel2? > (apart from being maintained, of course) >
There are 2 main (tech) differences: - Mongrel2 uses SUB/PUB (2 channel), BlastBeat uses ROUTER/DEALER, you only need one channel for request and response. - Mongrel2 put the whole request in a single message, this is easier but forces you to pass uploaded file as filenames (so backend must be on the same machine or need access to the mongrel2 machine) or to buffer into memory (for adding datas to the zeromq message). BlastBeat requires you to manage request content data assembling 'body' messages. So, 2 different approaches. In addition to this mongrel2 is a full featured webserver, an area in which BlastBeat does not want to compete :) -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
