<br><br><div><span class="gmail_quote">On 2/8/06, <b class="gmail_sendername">David Reid</b> <<a href="mailto:dreid@dreid.org">dreid@dreid.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Todd Thomas wrote:<br>> It does support wsgi, I was playing around with it. I went back to<br>> twisted-web, I like its lower level approach. Using http.request<br>> directly vs. resources is nice since I can pretty much tell exactly what
<br>> is going on. I love the fact that you can work at an extremely low level<br>> in twisted-web. I hope twisted-web2 doesn't get too high level.<br><br>I don't really understand this, twisted.web _has_ resources. They're
<br>not very good in that one resource is expected to return another<br>resource to consume the next segment in the path, which makes it hard to<br>stop the machinery. But if you mean what I think you mean (which I hope<br>
you don't) and that you're working with your own server.Site then I'd<br>say you need twisted.web2 more than anyone, because it's resource api<br>will allow you to make your framework work along side others. Which is<br>
one of the problems with current Nevow and part of the reason<br>twisted.web2 was started.<br><br>-David<br><br><br>_______________________________________________<br>Twisted-web mailing list<br><a href="mailto:Twisted-web@twistedmatrix.com">
Twisted-web@twistedmatrix.com</a><br><a href="http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-web">http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-web</a><br></blockquote></div>You
just described exactly the problem I am currently having with
twisted-web2. I tried to create wsgi as a root resource, however its
also dependent on static files in media directory. I wasn't able to
create a child object due to no matter what it passes full path to the
wsgi application. So then I made it a child of a root resource, this
sort of worked. But since the root path was consumed when it is passed
to the child resource, when the application does a redirect, it creates
the url in relation to root, not the child url. In my own application I
could work around this without too much difficulty since I already know
where my child is in relation to the root object.<br>