Hi,
I'm evaluating the possibility of adding rest config support for the
freemarker templates.
The simplest way to expose the template list that came to mind is to use
two resources,
template list and template, that would react to a path templated as follows:
<restConfigRoot>/templates/<workspace>/<store>/<resource>
where the bits in <workspace>/<store>/<resource> are all optional, so that
<restConfigRoot>/templates would list the global templates,
<restConfigRoot>/templates/<workspace> would list the per workspace
templates
and so on.
And then the single file could be retrieved/modified/deleted via:
<restConfigRoot>/templates/<workspace>/<store>/<resource>/<file.ftl>
I've also considered embedding /templates under each existing resource,
but it seems that would make it more difficult to integrate since we'd have
to add links in all lists, which at the time of writing are relative flat
and
made of catalog resources only.
Opinions?
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
-------------------------------------------------------
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
