W3C home > Mailing lists > Public > uri@w3.org > February 2010

RE: URI Template: query param name different than variable name

From: Manger, James H <James.H.Manger@team.telstra.com>
Date: Fri, 26 Feb 2010 15:14:09 +1100
To: "Roy T. Fielding" <fielding@gbiv.com>, "uri@w3.org" <uri@w3.org>
Message-ID: <255B9BB34FB7D647A506DC292726F6E11250B94539@WSMSG3153V.srv.dir.telstra.com>
I said:
>> '=' is currently used to introduce a default value:
>> {[op]var[=default]}. However, you don't need to use an operator and a
>> default together. For instance, in the current syntax "{?startPage=1}"
>> can be written as "?startPage={startPage=1} -- there is always a value
>> (from the variable or the default) so the operator-related parts will
>> always be present so they can be 'literals' outside the { } brackets.

Roy replied:
> I think that introducing a recursive syntax for templates
> would be dangerous.  Tempting, but a denial-of-service attack
> just waiting to happen.

I am not suggesting a recursive syntax.
In the example template
 "?startPage={startPage=1}"
the first 11 characters are literal characters to be copied into the URI being constructed -- they are not part of a {...} placeholder that a template processor replaces.
Received on Friday, 26 February 2010 04:14:52 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:14 UTC