[Pywps-dev] [REST] Multiple running server

[Jachym Cepicky]

Jonas: I believe, this is just flask issue, on apache this should work as
expected (flask can handle only singe request per time)

flask should not be used in production environment [1] -> Do not use the
builtin development server in production.

[1] http://flask.pocoo.org/docs/0.10/deploying/

st 22. 7. 2015 v 14:24 odesílatel Jonas Eberle <jonas.eberle at gmx.de> napsal:

> Hi Calin,
>
> do you also have in mind to publish several PyWPS instances on a single
> port? For operational use I am not keen on opening a new port for any PyWPS
> instance in the future. I would like to use WSGI with Apache Webserver to
> make my instances available. Will this still be available with these
> developments?
>
> I would like to organize my services as follows (path to configured in the
> settings or in the Apache configuration):
> http://localhost/wps1
> http://localhost/wps2
>
> For the REST administration interface I would then like to use, e.g.
> http://localhost/wpsadmin (path to be configured in settings or Apache
> configuration).
>
> Best regards,
> Jonas
>
> ----- Am 21. Jul 2015 um 17:23 schrieb Calin Ciociu <
> calin.ciociu at gmail.com>:
>
> Hello everyone,
>
> I wanted to know people's opinion on the way I am currently implementing
> the REST interface.
> Multiple server can be run and managed through the REST interface
> although every server runs with a different port.
> So in the end there will be multiple servers running like for example:
>
> http://localhost:5001/wps...
> http://localhost:5002/wps...
> http://localhost:5003/wps...
>
> On top of these a "sever" is already running which is handling REST.
> It is currently running on port 5000 (which can be also changed).
>
> To me this makes sense and seems straightforward.
> Is there a better approach?
> Should I continue like this?
>
>
> Best regards,
>
> Calin
> _______________________________________________
> pywps-dev mailing list
> pywps-dev at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/pywps-dev
>
>
> _______________________________________________
> pywps-dev mailing list
> pywps-dev at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/pywps-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pywps-dev/attachments/20150723/3b58d450/attachment.html>