On 3 February 2016 at 23:46, Niels Charlier <[email protected]> wrote:

> > - Instead of metadata, it would be (arguably) more RESTful to support
> > a HEAD operation. You have a header for Last-Modified, could add an
> > X-Parent and X-Type, and name could be deduced from the URL. Or is the
> > need for custom HTTP headers a red flag? (Not to mention the problems
> > passing these through the stack.) Andrea raised the issue of HEAD and
> > I do not recall seeing a response. Please state why you are not using
> > HEAD. The core need I see is for directory traversal. I dislike
> > parsing URLs to find a parent resource, but would that be more
> > RESTful? Is the use of a metadata parameter a REST best practice?
>
> I did send an email about the HEAD operation. Last-modified will be
> supported. I did not actually think of using custom http headers for the
> other fields. That is interesting. We can support both.
>

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 :)
------------------------------------------------------------------------------
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

Reply via email to