I've changed the proposal. I will research the HEAD proposal, but I'll
support ?metadata anyway (as it is extendible)
Regards
Niels
On 14-01-16 00:03, Jody Garnett wrote:
Correct, and tricky - wonder if our rest library supports that :)
Still human navigable html output our Json is not a bad thing.
On Wed, Jan 13, 2016 at 3:02 PM Robert Coup
<[email protected] <mailto:[email protected]>> wrote:
On 13 January 2016 at 22:48, Jody Garnett <[email protected]
<mailto:[email protected]>> wrote:
Agreed, I see the limitations - what do you think of Kevin's
idea of using a query string and avoid a parallel tree for
metadata?
Isn't that what HEAD requests are for? And return the metadata in
headers?
HEAD /resource/path/to/directory
> Last-Modified: <timestamp>
> Content-Type: application/x-directory
HEAD /resource/path/to/directory/file.png
> ETag: <md5 hash>
> Content-Length: 12345
> Last-Modified: <timestamp>
> Content-Type: image/png
Rob :)
--
--
Jody Garnett
------------------------------------------------------------------------------
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=267308311&iu=/4140
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
