Well my thought about the use case is not handling cases with
pre-configured layers such as this one but one that is fairily common one
among our clients that goes like this:
1. user (via rest api) posts a new layer to the server
2. user gets xml representation of the new layer to get all configuration
info
3. user uses config info, bounds, srs, etc... to make a proper OGC service
request
On Mon, May 28, 2012 at 11:35 AM, Andrea Aime
<[email protected]>wrote:
> > I can go for that, though I don't understand how it changes on the rest
> clients
> > side, since it merely changes a likeliness of getting the code, not
> > the fact that
> > the client is broken if it cannot handle WKT too.
>
> Point in case, here is topp:states featureType.xml, from svn:
>
> http://svn.codehaus.org/geoserver/trunk/data/release/workspaces/topp/states_shapefile/states/featuretype.xml
>
> If a client cannot handle one of our oldest demo layers... I would say
> it is broken.
>
> 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
>
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
