News for hackers. Stuff that matters.
Re:The Future of Python HTTP by detst on Monday April 02, 2012 @04:54PM (#3790032)
I don't understand your point and why it's the top comment. Sure, 0MQ is great and can be used in place of HTTP in some cases. But if you want to serve requests to a web browser, you have to speak HTTP at some point. These are the use cases they are handling.

It's not even a matter of preference; it's a matter of a need for HTTP and they are addressing this need, while apparently accounting for 0MQ (he mentions it in the post).

Also, you mention down-thread, "HTTP is the weaker of the two transports"; it's only "weaker" if you ignore any use case that involves communicating with a web browser.

Re:The Future of Python HTTP by j2labs on Monday April 02, 2012 @04:57PM (#3790049)
The involvement of the requests library signals that the consumer is not a web browser...
Re:The Future of Python HTTP by detst on Monday April 02, 2012 @05:31PM (#3790195)
No, it doesn't. It signals that unifying multiple code-bases and efforts containing clear overlap is a pretty smart idea. This project will still be used to serve requests from a web browser. It will also be used to make requests to HTTP services that the user has no control over.

Are you just trying to make an ideological argument that HTTP is used in cases when 0MQ might be a better option? If so, I agree but I just don't understand why you seem dismissive of this project when HTTP has its place and, therefore, this project has its place. The fact that 0MQ is mentioned in this post seems to indicate that the author understands 0MQ's place.

Re:The Future of Python HTTP by j2labs on Monday April 02, 2012 @07:46PM (#3790736)
I prefer ZMQ when I have the choice. ZMQ is better from an ideological perspective and better for infrastructure.

In cases where you can only use HTTP, this will be great, but if I have a choice I'd use ZMQ instead.

I don't mean to sound dismissive, but I am opinionated. I think Kenneth and Armin do great work. I'm sure this project will be excellent.

Re:The Future of Python HTTP by detst on Monday April 02, 2012 @10:11PM (#3791140)
I think our only disagreement is that you viewed it as a poor alternative for 0MQ and I viewed it as something else. Just a different perspective that I interpreted as taking away from what this announcement was really about but I suspect it wasn't your intention.
Re:The Future of Python HTTP by LeafStorm on Monday April 02, 2012 @05:20PM (#3790158)
No, but it does signal that the producer is a Web server. Those aren't going away anytime soon, either.
Re:The Future of Python HTTP by j2labs on Monday April 02, 2012 @07:46PM (#3790737)
As I said before: Ease in using HTTP itself is welcome, but I don't want to use it in my infrastructure. It's a band-aid for WSGI instead of a solution.