> I happen to already be working on a python client library for the REST API,
> currently hosted at http://bitbucket.org/dwins/gsconfigpy/ . It is far from
> complete, but I'd like to make sure that we are at least providing the same
> API in both access modes.
Well, we currently have 3 options: two implemented apis and one
planned. Of course, working code beats perfect plans so I am at
disadvantage here, but there should definitely be a discussion about a
reasonable API between all the pythonic libraries for Geoserver if we
want happy users.
dwins (Java like)
============
from geoserver.catalog import Catalog
self.cat = Catalog("http://localhost:8080/geoserver/rest";)
sf = cat.getWorkspace("sf")
sfdem = self.cat.getStore("sfdem", sf)
jdeolive (Dictionary based)
===================
from geoserver import Catalog
sf = Catalog('sf')
sfdem = sf["sfdem"]
ingenieroariel (Django ORM like)
=======================
from geoserver import catalog
sf = catalog.workspaces.get("sf")
sfdem = sf.stores.get("sfdem")
--
Ariel Núñez
GeoSolutions = http://geo-solutions.it
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
