cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Donald Ball <ba...@webslingerZ.com>
Subject Re: [RT] resource views, error handling, pipeline debugging
Date Thu, 29 Jun 2000 17:32:57 GMT
On Thu, 29 Jun 2000, Stefano Mazzocchi wrote:

>   3) resource (what Niclas proposes)
> 
>      path/resource -> normal view
>      path/resource/tracing -> tracing view
> 
>   4) query (what I proposed)
> 
>      path/resource -> normal view
>      path/resource?cocoon-view="tracing" -> tracing view
> 
> the first 2 are not directly controllable by Cocoon.
> 
> So the choice is between 3 and 4.
> 
> Admittedly, 3 has some advantages since it's independent on the HTTP
> action and can be safely included in links, but also disadvantages since
> it could create naming conflicts.
> 
> Hmmm, I would like to know your comments on this before stating my vote.

Either way you get the possibility of name collision, right? at least you
can change the magic variable name in 4. i'd go that route.

> >(Stefano is not Mohammed - Why go to the mountain, when
> > you can turn it... :o)
> 
> I know somebody would have said that, I just wanted to see who was the
> first one :)
> 
> I guess the mountain twisting idea shows my egocentricy, doesn't it? :)

first there is a mountain
then there is no mountain
then there is

- donald


Mime
View raw message