On Fri, 18 Nov 2005 15:47:02 -0600, Clark C. Evans <[EMAIL PROTECTED]> wrote:

Glyph,

Thank you for taking time to discuss this more.  I think I disagree that
twisted core currently is, or should be an object publishing system.
It's ok if Nevow is an object publishing system; but you should not
restrict the applications of twisted.web2 to object publishing.

By an "object publishing system", I mean a system where every object
in the system is a Resource, and hence has a *unique* URL.  That is,
if I have two distinct objects in the system, they have different
URLs; and if I have two URLs that refer to actual resources in the
system, they refer to different objects.
look like (to phrase it with your definition)?

Just a comment from the peanut-gallery: As a person who is currently using web2, I want to weigh in heavily on the side of "restrict the applications of twisted.web2 to object publishing". The way in which web2 publishes objects fits very nicely with the way Roy Fielding describes REST, at least insofar as my understanding of REST goes.

Every Resource *should* be identified by a URL, and that URL *should* refer to one logical Resource. This is how the web works today; I for one, hope that it continues to do so.

That said, I'm completely in favor of coming up with sane mechanisms for Sessions and Auth. Changing web2 such that the a singly-rooted tree of Resources is no longer the base metaphor should not be a requirement for implementing Sessions and Auth.

It seems to me that you'd be much happier with a WSGI solution, wherein you can just plug your request-processing, session-handling, foo-handling components into the stream at appropriate places. Web2 supports WSGI already, so that might be a better route to take. Then you can implement the model that best suits your application, while leaving web2's object publishing model intact for those of us that vastly prefer it.

L. Daniel Burr

_______________________________________________
Twisted-web mailing list
[email protected]
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-web

Reply via email to