55 messages in org.apache.incubator.sling-devRe: Simplifying script paths and names?| From | Sent On | Attachments |
|---|---|---|
| Bertrand Delacretaz | Apr 14, 2008 8:45 am | |
| Carsten Ziegeler | Apr 14, 2008 9:11 am | |
| Alexander Klimetschek | Apr 14, 2008 9:25 am | |
| Carsten Ziegeler | Apr 16, 2008 1:00 am | |
| Bertrand Delacretaz | Apr 16, 2008 5:43 am | |
| Carsten Ziegeler | Apr 16, 2008 5:52 am | |
| Felix Meschberger | Apr 16, 2008 8:11 am | |
| Carsten Ziegeler | Apr 16, 2008 9:09 am | |
| Carsten Ziegeler | Apr 16, 2008 11:20 pm | |
| Bertrand Delacretaz | Apr 17, 2008 12:00 am | |
| Gert Vanthienen | Apr 17, 2008 12:49 am | |
| Juanjo Vázquez | Apr 17, 2008 1:33 am | |
| Alexander Klimetschek | Apr 17, 2008 1:48 am | |
| Michael Marth | Apr 17, 2008 6:39 am | |
| Bertrand Delacretaz | Apr 18, 2008 12:21 am | |
| Bertrand Delacretaz | Apr 18, 2008 12:24 am | |
| Felix Meschberger | Apr 18, 2008 12:56 am | |
| Michael Marth | Apr 18, 2008 1:33 am | |
| Bertrand Delacretaz | Apr 18, 2008 1:36 am | |
| Bertrand Delacretaz | Apr 18, 2008 1:43 am | |
| Felix Meschberger | Apr 18, 2008 2:10 am | |
| Bertrand Delacretaz | Apr 18, 2008 2:16 am | |
| Felix Meschberger | Apr 18, 2008 4:18 am | |
| Carsten Ziegeler | Apr 18, 2008 4:59 am | |
| Felix Meschberger | Apr 18, 2008 5:54 am | |
| Bertrand Delacretaz | Apr 18, 2008 5:58 am | |
| Felix Meschberger | Apr 18, 2008 6:16 am | |
| Bertrand Delacretaz | Apr 18, 2008 6:19 am | |
| Carsten Ziegeler | Apr 18, 2008 6:21 am | |
| Felix Meschberger | Apr 18, 2008 6:45 am | |
| Carsten Ziegeler | Apr 18, 2008 6:53 am | |
| Bertrand Delacretaz | Apr 18, 2008 6:53 am | |
| Felix Meschberger | Apr 18, 2008 7:06 am | |
| Felix Meschberger | Apr 18, 2008 7:07 am | |
| Carsten Ziegeler | Apr 18, 2008 7:11 am | |
| Carsten Ziegeler | Apr 18, 2008 7:22 am | |
| Felix Meschberger | Apr 18, 2008 7:30 am | |
| Carsten Ziegeler | Apr 18, 2008 7:35 am | |
| Felix Meschberger | Apr 18, 2008 7:43 am | |
| Carsten Ziegeler | Apr 18, 2008 7:49 am | |
| Tobias Bocanegra | Apr 18, 2008 9:33 am | |
| David Nuescheler | Apr 25, 2008 7:40 am | |
| Felix Meschberger | Apr 25, 2008 8:52 am | |
| Tobias Bocanegra | Apr 25, 2008 9:35 am | |
| Dominik Süß | Apr 25, 2008 10:09 am | |
| Dominik Süß | Apr 25, 2008 12:07 pm | |
| Carsten Ziegeler | Apr 26, 2008 10:16 am | |
| Tobias Bocanegra | Apr 26, 2008 10:45 am | |
| Dominik Süß | Apr 26, 2008 1:45 pm | |
| Tobias Bocanegra | Apr 26, 2008 2:14 pm | |
| David Nuescheler | Apr 27, 2008 4:37 am | |
| Bertrand Delacretaz | Apr 28, 2008 6:21 am | |
| Felix Meschberger | Apr 28, 2008 6:40 am | |
| Felix Meschberger | Apr 28, 2008 8:33 am | |
| Bertrand Delacretaz | Apr 29, 2008 12:50 am |
| Subject: | Re: Simplifying script paths and names? | |
|---|---|---|
| From: | Bertrand Delacretaz (bdel...@apache.org) | |
| Date: | Apr 18, 2008 1:43:53 am | |
| List: | org.apache.incubator.sling-dev | |
On Fri, Apr 18, 2008 at 9:56 AM, Felix Meschberger <fmes...@gmail.com> wrote:
...{scriptPathPrefix}/{resourceTypePath}/{resourceTypeLabel}.{selectorString}.{requestMethod}.{requestExtension}.{scriptExtension}.
+1
My concern now is, how do we weight these parts:
{scriptPathPrefix}/{resourceTypePath} - Required, scripts will otherwise not be found
ok
{resourceTypeLabel} - optional, resolve doesn't care, that is no preference
I'd make it required, to avoid having too many options. We can always make it optional later, while the opposite would not be backwards-compatible.
{selectorString} - Better is longer match
ok
{requestMethod} - Better is to have it, required for non-GET {requestExtension} - Better is to have it
I'd use my suggested rules as the only options here:
rule A) {requestMethod}.{requestExtension} == "GET.html" -> required to use an empty string
rule B) {requestMethod} != "GET" or "HEAD" -> {requestExtension} is optional
I think this reduces the set of possible combinations, and the rules are based on safe vs. unsafe http methods, so that's not too bad.
{scriptExtension} - resolve only cares insofar as to find a ScriptEngine
ok
Now, given a GET request to bar.print.a4.html, what is the priority order for the following (porential) script names ?
(1) .../print.esp (2) .../print.a4.esp (3) .../print.html.esp (4) .../print.GET.html.esp (5) .../print.a4.html.esp (6) .../print.a4.GET.html.esp
It would probably be (6) - (5) - (2) - (4) - (3) - (1)
Yes, more specific names should always win over less-specific ones. But with my above suggested rules, only the following names would be allowed (in priority order):
print.a4.esp print.esp
This is a good example of how my rule A) reduces the number of possible combinations, that does not matter too much for the implementation, but it's IMHO easier to explain.
-Bertrand