On 29/08/2008, at 11:20 PM, Henrik Nordstrom wrote:
On fre, 2008-08-29 at 10:44 +1000, Mark Nottingham wrote:
I'm not convinced it's a great solution, but something like URISpace
may be appropriate;
http://www.w3.org/TR/urispace.html
Not very different in function, besides being XML..
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tres Seaver wrote:
Mark Nottingham wrote:
I'm not convinced it's a great solution, but something like URISpace
may be appropriate;
http://www.w3.org/TR/urispace.html
What's nice about this is that you buy some efficiency by walking down
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tres Seaver wrote:
Tres Seaver wrote:
Mark Nottingham wrote:
I'm not convinced it's a great solution, but something like URISpace
may be appropriate;
http://www.w3.org/TR/urispace.html
What's nice about this is that you buy some efficiency
On fre, 2008-08-29 at 10:44 +1000, Mark Nottingham wrote:
I'm not convinced it's a great solution, but something like URISpace
may be appropriate;
http://www.w3.org/TR/urispace.html
Not very different in function, besides being XML..
However, the URISpace xml tag space is a bit too
On fre, 2008-08-29 at 08:38 +0800, Adrian Chadd wrote:
Make sure you can collapse those ACLs down to something sensible for
software processing before you go down that path!
It's relatively easy to make a unified lookup tree of such structure,
and even if you don't it's still as fast or faster
2008/8/30 Henrik Nordstrom [EMAIL PROTECTED]:
Make sure you can collapse those ACLs down to something sensible for
software processing before you go down that path!
It's relatively easy to make a unified lookup tree of such structure,
and even if you don't it's still as fast or faster than
Mark Nottingham wrote:
One of the things that came up in Sydney briefly was whether the
stale-while-revalidate and max-stale refresh_pattern options would be
better expressed as ACLs.
Taking this a bit further, could/should the same be true of the rest of
the refresh_pattern options (and
I vision a nested tree of matches (acl) and operators
(allow/deny/refresh_pattern/outgoing_ip/tos/no-cache/ignore-xxx/deny_info/logmessage/peergroup/...).
But it requires a different parser which is not single line oriented as
you can not express a tree on a single line in a meaningful
2008/8/29 Kinkie [EMAIL PROTECTED]:
YES please..
I'm quite familiar with the JunOS ACL format and it resembes this
pretty closely, it's very flexible..
Make sure you can collapse those ACLs down to something sensible for
software processing before you go down that path!
Adrian
I'm not convinced it's a great solution, but something like URISpace
may be appropriate;
http://www.w3.org/TR/urispace.html
What's nice about this is that you buy some efficiency by walking down
the tree, rather than evaluating a linear set of rules...
Cheers,
On 29/08/2008, at 10:38
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Nottingham wrote:
I'm not convinced it's a great solution, but something like URISpace
may be appropriate;
http://www.w3.org/TR/urispace.html
What's nice about this is that you buy some efficiency by walking down
the tree, rather
One of the things that came up in Sydney briefly was whether the stale-
while-revalidate and max-stale refresh_pattern options would be better
expressed as ACLs.
Taking this a bit further, could/should the same be true of the rest
of the refresh_pattern options (and perhaps of the patterns
12 matches
Mail list logo
