J2 Labs

Y U NO USE WSGI?

BRUBECK CAN NOW

class DemoHandler(WebMessageHandler):
    def get(self):
        name = self.get_argument('name', 'dude')
        self.set_body('Take five, %s!' % name)
        return self.render()

config = {
    'msg_conn': WSGIConnection(),
    'handler_tuples': [(r'^/brubeck', DemoHandler)],
}

app = Brubeck(**config)
app.run()

NO MONGREL2

$ ./demo_wsgi.py 
INFO:root:Using coroutine library: gevent
Brubeck v0.3.9 online ]-----------------------------------
Serving on port 6767...

That’s it. You’re running. It’s using either gevent.wsgi or eventlet.wsgi so all the non-blocking goodness is still all there.

Y U NO USE MONGREL2?!

HELP

Thanks to Thomas Ballinger and Steven Ciraolo for writing most of the code. I can’t wait to see what they’re up to next.

TRYING IT

The latest work is in the wsgi_support branch. There is a demo_wsgi.py, which doesn’t require Mongrel2 or ZeroMQ and, by default, starts on port 6767.

I will probably move it into master after we’ve done some more testing on it.

ON WSGI

I must admit, I am a little bummed to include WSGI support when I believe Mongrel2 is the rightest way to do web serving, but I am happy to open Brubeck itself up to more people. I also hope they will give Mongrel2 consideration when deploying Brubeck in production environments.

On the other hand, I am happy to include another point that Brubeck is aware of, yet agnostic towards. If you have a different opinion on the web server from me, well, I guess we can accomodate that. It’s 50 lines of Python, in the new design, so whatever… I’m in!

It will surely be fun to compare WSGI vs ZMQ, now that we have something of a control on the rest of the framework. SCIENCE.

Edit: @jiaaro has pointed out that the wsgi_support still requires zmq to be installed by nature of how the imports work. Drat, I didn’t think of that. I will fix that before this branch is merged into master.