I imagine a plugin system, similar to Qgis Desktop, where every service is discovered/registered if available in certain library paths.<div><br></div><div>For the Python side I see two features that could be supplied:</div>
<div><br></div><div> - 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</div><div> - 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</div>
<div><br></div><div>giovanni<br><br><div class="gmail_quote">2011/10/20 Martin Dobias <span dir="ltr"><<a href="mailto:wonder.sk@gmail.com">wonder.sk@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Wed, Oct 19, 2011 at 7:17 PM, G. Allegri <<a href="mailto:giohappy@gmail.com">giohappy@gmail.com</a>> wrote:<br>
> That would ne a very interesting architecture Martin.<br>
> Each Service would manage its on requirements, for example its own internal<br>
> bindings to Python or whatever.<br>
> I'm not sure about the "fastgi nature" of the services. The server has a an<br>
> fcgi interface, ok, but the services should be indipendent from this<br>
> specific interface. The Server could be deployed in a different fashion, but<br>
> the services should ignore this.<br>
<br>
</div>Sure, it does not have to be bound specifically to FastCGI so that in<br>
future other gateway interfaces could be used.<br>
<font color="#888888"><br>
Martin<br>
</font></blockquote></div><br></div>