On Wed, Jul 11, 2012 at 8:37 PM, Juan Marín Otero <
[email protected]> wrote:
> Andrea / Justin,
>
> Thanks for the feedback, I actually went back and forth with this a bit
> but ended up doing it the way the patch reflects and I don't even remember
> my reasoning but yours is sound, this should be an easy change. Am I
> reading correctly in that you consider that POST should not be used for any
> of these additional resources?
>
Err.. I guess not. I mean, when a resource location is 100% predictable and
there is even a finite set of them,
POST seems overkill. Just my two cents, I'm not a REST guru
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
------------------------------------------------------------------------------
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
