On Wed, Jan 25, 2012 at 10:57 PM, Gabriel Roldan <grol...@opengeo.org>wrote:
> Yeah, the concern makes complete sense.
>
> My hope is (with proper documentation) this makes it simpler. Like in
> if you want to configure a cached layer through the REST API, you
> should use the GWC REST API. And the way to do that is by having a
> steady xml/json representation of it. Storing it on the layer's
> metadata is a (very) convenient way of avoiding an extra storage
> mechanism for such a tightly coupled resource. But still I think the
> proper way to configure a cached layer for a geoserver layer would be
> through the gwc api. Makes sense?
>
>
It does, yet at the same time we cannot avoid people to work against
the version embedded in the layer definition since it's out there and
right in their face.
Btw, don't know much about GWC rest api: how well is it integrated
with the GeoServer one? Thinking about security here, for example.
I honestly did not know the integrated GWC was exposing a rest api
to start with
Cheers
Andrea
--
-------------------------------------------------------
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 339 8844549
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
-------------------------------------------------------
------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
