Thanks Andrea, all good feedback - these proposals end up being design
documents after all.
I don't think I know enough about how rest path mappers work to understand
the difference between config and data. Internally the ResourceStoreAPI is
used to access config, and a different GeoServerDataDirectory method is
used to resolve relative URLs into a file reference for data access.
I had a similar question with respect to the difference between "config"
and "catalog" - consider using this rest api in the styles folder - we want
to access the "sld" and "font" files, but ignore the "xml" files used by
the catalog configuration - since they are stored elsewhere/available by
another rest api.
--
Jody Garnett
On 27 January 2016 at 01:48, Andrea Aime <[email protected]>
wrote:
> Hi Jody,
> -1 for the moment, but only because the proposal is incomplete.
>
> Bits that should be addressed before making it go forward:
> * Show the XML and JSON representations of the various resources and
> commands (are they properly interlinked via atom links, and what other
> information do they contain?). This is the most evident limitation of the
> proposal, as these are not implementation bits, but rightful part of the
> protocol you're proposing to implement
> * Determine what happens if format is used against a file resource (that I
> assume we cannot transcode to another format), and what mime type will be
> returned for them (e.g., property files)
> * What is the metadata of a directory? I assume we can return metadata for
> a file too, but the proposal only mentions a format for directories
> * How does one tell apart the desire to upload a zip file, from one of
> uploading a directory to be unpacked? How does one create an emtpy
> directory?
> * I don't claim to be a REST expert, but the POST usage seems strange...
> should't POST be used only when the target resource position is determined
> by the server instead of by the caller? Some guidance here:
> http://restcookbook.com/HTTP%20Methods/put-vs-post/
> * HEAD requests for metadata seem a good idea
>
> Finally, a general question, how is the resource work going to interact
> with the existing rest path mappers? What if for example one wants to
> upload via
> the REST api some large data set to be configured, and make sure it's
> going to be saved on disk instead of DBMS, because it needs to accessed
> via random access and it's in general very large?
> My understanding is that JDBCConfig would only handle _config_ and not
> data, but want to make sure.
>
> Cheers
> Andrea
>
>
> On Tue, Jan 26, 2016 at 10:51 PM, Jody Garnett <[email protected]>
> wrote:
>
>> Here is the proposal from Niels:
>> https://github.com/geoserver/geoserver/wiki/GSIP-137
>>
>> +1 the proposal has been revised addressing my earlier questions.
>>
>> --
>> 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
>>
>>
>
>
> --
> ==
> GeoServer Professional Services from the experts! Visit
> http://goo.gl/it488V for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions S.A.S.
> Via Poggio alle Viti 1187
> 55054 Massarosa (LU)
> Italy
> phone: +39 0584 962313
> fax: +39 0584 1660272
> mob: +39 339 8844549
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*
>
> Le informazioni contenute in questo messaggio di posta elettronica e/o
> nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
> loro utilizzo è consentito esclusivamente al destinatario del messaggio,
> per le finalità indicate nel messaggio stesso. Qualora riceviate questo
> messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
> darcene notizia via e-mail e di procedere alla distruzione del messaggio
> stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
> divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
> utilizzarlo per finalità diverse, costituisce comportamento contrario ai
> principi dettati dal D.Lgs. 196/2003.
>
>
>
> The information in this message and/or attachments, is intended solely for
> the attention and use of the named addressee(s) and may be confidential or
> proprietary in nature or covered by the provisions of privacy act
> (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
> Code).Any use not in accord with its purpose, any disclosure, reproduction,
> copying, distribution, or either dissemination, either whole or partial, is
> strictly forbidden except previous formal approval of the named
> addressee(s). If you are not the intended recipient, please contact
> immediately the sender by telephone, fax or e-mail and delete the
> information in this message that has been received in error. The sender
> does not give any warranty or accept liability as the content, accuracy or
> completeness of sent messages and accepts no responsibility for changes
> made after they were sent or for other risks which arise as a result of
> e-mail transmission, viruses, etc.
>
> -------------------------------------------------------
>
------------------------------------------------------------------------------
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
