Phil Archer wrote:
The problem is finding the right amount of flexibility without making it
too complicated or opening unwanted security holes.
...
It depends on your use cases of course.
I guess the reason I've joined this discussion is that I'm concerned
that most of the schemes out there
07, 2009 12:52 PM
To: public-webapps WG
Cc: Phil Archer; Scott Wilson; Dominique Hazael-Massieux; Marcin Hanclik
Subject: Re: [WARP] uri attribute is confusing
Phil Archer wrote:
The problem is finding the right amount of flexibility without making it
too complicated or opening unwanted security
Hazael-Massieux [...@w3.org]
Sent: Wednesday, September 23, 2009 3:19 PM
To: public-webapps@w3.org
Cc: ph...@w3.org
Subject: [WARP] uri attribute is confusing
Hi,
The attribute uri on the access element in WARP is somewhat
misleading - what it takes is more a URL pattern than a URI. I would
: ph...@w3.org
Subject: [WARP] uri attribute is confusing
Hi,
The attribute uri on the access element in WARP is somewhat
misleading - what it takes is more a URL pattern than a URI. I would
suggest renaming it in urlpattern or just pattern (unless there
are
already many implementations
-Massieux [...@w3.org]
Sent: Wednesday, September 23, 2009 3:19 PM
To: public-webapps@w3.org
Cc: ph...@w3.org
Subject: [WARP] uri attribute is confusing
Hi,
The attribute uri on the access element in WARP is somewhat
misleading - what it takes is more a URL pattern than a URI. I would
suggest
2009/9/23 Dominique Hazael-Massieux d...@w3.org:
Hi,
The attribute uri on the access element in WARP is somewhat
misleading - what it takes is more a URL pattern than a URI. I would
suggest renaming it in urlpattern or just pattern (unless there are
already many implementations that rely on
Hi,
The attribute uri on the access element in WARP is somewhat
misleading - what it takes is more a URL pattern than a URI. I would
suggest renaming it in urlpattern or just pattern (unless there are
already many implementations that rely on that attribute name).
There may be lessons to be
