On 2/7/06, James Y Knight
On Feb 7, 2006, at 4:09 AM, Todd Thomas wrote:
I find them extemely handy personally, how else are you going add resources without resorting to restarting the server? But I guess depends on what you are using them for. I tend to use twisted more for testing and experimenting, simpler than installing apache. Unfortunately twisted-web doesnt have a wsgi implementation, I have been messing around with django a bit trying to see how modular the code is.
You'll notice that I said I was open to them still being supported. I'll take a submission of code + unit tests for it, or if not, will get around to implementing it someday.
I'll also note, it should be possible to use twisted.web.script from within a twisted.web2 server, although you won't be able to use web2 Resources in the rpys loaded by the twisted.web.script loader. (The compatibility only works one way -- you can use old resources inside new ones, but not new ones inside old ones).
I think you might have meant this but it wasn't entirely clear so I'll also note that twisted.web2 does support wsgi.
James
_______________________________________________ Twisted-web mailing list Twisted-web@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-web
It does support wsgi, I was playing around with it. I went back to twisted-web, I like its lower level approach. Using http.request directly vs. resources is nice since I can pretty much tell exactly what is going on. I love the fact that you can work at an extremely low level in twisted-web. I hope twisted-web2 doesn't get too high level. Resources are great when your making a standalone web app, but not so great when you are wanting to build frameworks on top of them. The biggest attraction for me in twisted is the fact that it pretty much allows you freedom to do anything. I am considering writing a wsgi handler for twisted-web. I think it would be a good project.