cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicola Ken Barozzi <>
Subject Re: defaulting to a matcher when another one is not present
Date Tue, 15 Oct 2002 16:50:23 GMT
Hunsberger, Peter wrote:
> shows you voting -1 on this issue ????  If that's not correct, or you'd like
> to revoke your vote, then forget the whole issue...

My vote was about breaking existing systems.
You said that you would put an attribute "switch" for it, so that 
effectively makes my -1 invalid.

I'm just trying to come to a better solution that does not involve URI 
contracts that are not *clearly* defined in the sitemap.

> [rest of discussion snipped since it discusses how to share information and
> not how to share matching capabilities]

I don't like to give indipendent coders the possibility of sharing 
matching capability in different sitemap files.
But I continued this thing because I see that you have a point somewhere 
in the mails, but I don't like the solution you propose nor I see how 
this fits in Cocoon URI management from a broader perspective than just 
you departmental needs.

I gave you concrete possibilities you can use *now*, like xml entities, 
but you haven't even commented them, and this makes it clear that you 
don't give a damn about understanding my points and trying to address 
the issues I see.

Don't think I will continue this discussion, because I will not.
Sorry, but I reached my limit.
Find someone else for your problems.

Nicola Ken Barozzi         
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)

To unsubscribe, e-mail:
For additional commands, email:

View raw message