Gianugo Rabellino wrote:
On Apr 10, 2005 4:24 PM, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote:
Sylvain Wallez wrote:
So, although we may accept a new "context" attribute (I'm currently -0.9I'm -1 as well. (that was easy to guess ;-)
for this), I'm -1 for accepting dynamically generated sitemaps.
Uhm, first of all I'd say that the "context" attribute could be really
useful in contexts other than dynamic sitemaps, so I'd welcome that
addition. WRT dynamic sitemaps, I don't quite have a real opinion, I
can clearly see how it might lead to abuse, but I also tend to think
that Cocoon, as a framework, should allow applications built on top of
it using subsets of functionalities abstracted in high level
configuration files. However, if it's agreed once and for all that
dynamic sitemaps are to be considered harmful, so be it and let's
enforce it: it slipped through already, and now it doesn't work
anymore because of a bug. A check failing with an error message would
be enough to prevent stupid people like me to try it again in the
future (even though there will always be the http route...).
Well, as long as there is the http route, blocking "cocoon:" will just lead people to use an uglier workaround which you just engraved in the archives for posterity ;-)
So if we're to enforce something, it should be that a sitemap is a file, or a classpath resource (yes, I have this usecase).
Sylvain
-- Sylvain Wallez Anyware Technologies http://apache.org/~sylvain http://anyware-tech.com Apache Software Foundation Member Research & Technology Director
