I think custom headers are fine, it's just that if someone is using them in
practice they'll know to expect them :)
RESTful directories (IMO) should be self-documenting: the parent of /a/b/c
is /a/b and so on...
AFAICT there's nothing special in the metadata proposal that couldn't be
dealt with via:
Content-Type: application/directory (or of a file)
Last-Modified: <timestamp>
(sure, XML/JSON for consistency/other reasons is fine).
Whether it's a file or directory, the parent resource comes from the next
path segment...
Rob :)
On 10 February 2016 at 15:24, Ben Caradoc-Davies <[email protected]> wrote:
> On 09/02/16 08:14, Robert Coup wrote:
>
>> fyi, the "X-" prefix for custom headers is not the recommended approach
>> any
>> more... http://tools.ietf.org/html/rfc6648#section-3
>> *Recommendations for Creators of New Parameters*
>> Creators of new parameters to be used in the context of
>>
>>> application protocols:
>>> 1. SHOULD assume that all parameters they create might
>>> become standardized, public, commonly deployed, or usable across multiple
>>> implementations.
>>> 2. SHOULD employ meaningful parameter names that they have reason
>>> to believe are currently unused.
>>> 3. SHOULD NOT prefix their parameter names with "X-" or
>>> similar constructs.
>>>
>> Rob :)
>>
>
> Thanks for the link, Rob. That is a good point. I felt that custom headers
> are a bad idea and was soliciting suggestions for best-practices for
> RESTful directory traversal with HEAD to find a parent. Surely someone has
> tried this? Or is it an acceptable practice to assume that HTTP URLs can be
> parsed to remove trailing path elements?
>
> Kind regards,
>
>
> --
> Ben Caradoc-Davies <[email protected]>
> Director
> Transient Software Limited <http://transient.nz/>
> New Zealand
>
--
Chief Technical Officer Koordinates
+44 759 987 3480 <+44%20759%209873480> / koordinates.com / @koordinates
<https://twitter.com/koordinates>
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
