Felix Meschberger wrote:
Hi,
Am Montag, den 14.04.2008, 16:27 +0200 schrieb Carsten Ziegeler:
Felix Meschberger wrote:
The goal of URIs is to read and send them easily. For this reason any
special characters, in particular characters needing some form of
encoding should be prevented (if at all possible).
The current filter allows these characters:
"abcdefghijklmnopqrstuvwxyz0123456789_"
Now, I still think we have two use cases:
a) generate url friendly node names
b) try to generate exactly a specified node name
We can't unify these two cases into one. Therefore I think we should
handle the "nameHint" different from the support of using "jcr:title"
and the like to defer the node name.
Perhaps renaming "nodeName" to "nodeHint" was wrong after all...
Ok, my proposal is:
a) sling:post:nodeName - only invalid chars are filtered
b) sling:post:nameHint, jcr:title etc. are handled all the same (as they
are already today)
WDYT?
+1 (Bertrand suggested essentially the same, so I am also +1 to
Bertrand's proposal ;-) ). Withone catch, though: Can we find something
else than "nodeName" ? How about "exactName" ?
Just name? We have nameHint, so "name" would be correct, I think
And then, I would not filter or otherwise mangle the exact name (this is
the difference to Betrand's proposal) and rather fail if the name is
invalid.
Yepp, I agree. I'll update the issue and then change the impl.
Thanks
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
