I imagine a plugin system, similar to Qgis Desktop, where every service is discovered/registered if available in certain library paths.
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 giovanni 2011/10/20 Martin Dobias <wonder...@gmail.com> > On Wed, Oct 19, 2011 at 7:17 PM, G. Allegri <gioha...@gmail.com> wrote: > > That would ne a very interesting architecture Martin. > > Each Service would manage its on requirements, for example its own > internal > > bindings to Python or whatever. > > I'm not sure about the "fastgi nature" of the services. The server has a > an > > fcgi interface, ok, but the services should be indipendent from this > > specific interface. The Server could be deployed in a different fashion, > but > > the services should ignore this. > > Sure, it does not have to be bound specifically to FastCGI so that in > future other gateway interfaces could be used. > > Martin >
_______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer