L. Daniel Burr ha scritto: > [...] > Sorry, I realize terminology can be imprecise and confusing in many > cases. "template-per-segment", as I am using it, means this: each > segment in the URL corresponds to an HTML/XML/XHTML/Whatever template. >
Ok. > In nevow, this does not have to be the case. A resource might only > return child resources, and have no template of its own. In fact, > this is one of the really useful things about the tree-of-resource > structure: Some resources have concrete representations, and some > are purely logical. > Yes, this is very useful. > The point I am trying to make, and have apparently failed to make, > is that URL segment != markup snippet. This is clear, IMHO. A IResource has not only renderHTTP, but also locateChild. > A "template-per-segment" > design means that every segment must have a corresponding template > that gets rendered as some kind of markup. It also means that each > template depends on markup from the template containing it, which > is what I am objecting to so strenuously. > Here, again, I don't understand. What means that "each template depends on markup from the template containing it"? > Also, your statement that "baz" depends upon "foo" and "bar" is not > necessarily true. "baz" is clearly contained within "bar", which is > contained within "foo". Containment != dependency. This does not > preclude enforcing a dependency if you so desire, but I think that > mandating such a dependency is unnecessary and limiting. > > Is this explanation any clearer? > Yes, thanks. Regards Manlio Perillo _______________________________________________ Twisted-web mailing list [email protected] http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-web
