Hurl
hurl.it
hurl.it
You can check out this video to learn more about hurl http://vimeo.com/6238577
Using a fork per request is the easy way out. The problem as you've all seen, is that memory will be used up very very quickly.
The solution is to rewrite the app to use an event loop like select or epoll, or to queue the requests in a message queue: doable, but worth the effort? I doubt it, since the website looks like a hobby rather than a commercial product.
That is, if someone forks hurl (http://github.com/defunkt/hurl) and rewrites it to use one of the fixes you referred to above, I'm sure they'd merge that in and deploy that.
Doing it with Resque would make a lot of sense since hurl uses Redis already.
I'm saying that's probably why Chris and Leah haven't fixed it already and probably for many days to come.
It's open sourced, and contains some great code: http://github.com/defunkt/hurl. I used it as an inspiration when working on my first Redis project using Sinatra.
Rex Swain's HTTP Viewer - See exactly what an HTTP request returns to your browser:
Since both my app and this website have unavoidable network delays, I think I'll be retiring my program. That is, when the "Cannot allocate memory" bug gets fixed.
Has the added benefit of working on stuff you are developing on your own machine.
Plus, my experience (as a novice Pythonista) trying to get http basic auth working with urllib was hell. It takes like 5 obscure lines, you have to know the "realm", which I didn't even know about before. That's way more complicated than just typing stuff into text boxes