FYI, cocoon already outputs a "X-cocoon:" HTTP header that "markets" our presence in every request it handles. So, if we really want to know if cocoon handles that resource look at the HTTP headers, they don't break content length and are much more "REST"-ish.
I know about header add of course, but as I suppose amout of people that can lookup HTTP headers is just vestigal in comparison to amount of people that are able to lookup the HTML source. That's just my 2 cents.
IMO as soon as this gets added, someone will want it turned off (like me), and then we're back at ground zero. Best to leave it as a header, I think.
It's optional - even now. There is only a problem with the content length header when using this feature.
Joerg
