2011/10/20 Martin Dobias <[email protected]> > On Thu, Oct 20, 2011 at 4:00 PM, G. Allegri <[email protected]> wrote: > > I imagine a plugin system, similar to Qgis Desktop, where every service > is > > discovered/registered if available in certain library paths. > > I am not sure if such implicit (automatic) registration would be good. > Imagine that you have several web services. You would like to run a > public WMS server and also another bunch of services for a limited > group of users. Having all the services available in both instances > would not be very good - e.g. with a WMS server you may automatically > provide WPS server.
Looking at similar architectures, Geoserver seems to work this way, leaving to a security/configuration layer to enable and control the availability of the extensions. Anyway, we can avoid an automatic discovering, and control their exposure through a configuration system (eg a simple configurations file). > > > For the Python side I see two features that could be supplied: > > - Provide a qgispython to the services that require it to run python > > scripting. We can reuse a code very similar (the same?) as in Qgis > Desktop > > - Design a Python interface to "control" the Server. This would permit > to > > write Python frontends to the server, and incorporate Qgis Server inside > > Python server projects > > As noted in an earlier mail this is mostly just a matter of providing > wrappers for the server/service interfaces. > I agree > > Martin >
_______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
