Graham Dumpleton wrote:
.
requests.
If the work is indeed long running, the backend process would normally
just acknowledge the request and not wait. The web page would return
and it would be up to user to then somehow occassionally poll web
server, manually or by AJAX, to see how progre
On Feb 12, 9:19 am, Robin wrote:
> On Feb 11, 7:59 pm, Graham Dumpleton
> wrote:
>
>
>
> > On Feb 11, 8:50 pm, Robin wrote:
>
> > > Hi,
>
> > > I am building some computational web services using soaplib. This
> > > creates a WSGI application.
>
> > > However, since some of these services are co
>
>
> GAE is definitely not suitable in this case... The servers are
>> provided and maintained as part of a large scientific project for
>> which I am providing just a few services... Other groups are running
>> services in other platforms on tomcat through soaplab/instantsoap -
>> but I was hopin
On Feb 11, 9:32 pm, Graham Dumpleton
wrote:
> 2009/2/12 alex goretoy :
>
> > GAE (Google App Engine) uses WSGI for webapps. You don't have to overhead of
> > managing a server and all it's services this way as well. Just manage dns
> > entries. Although, there are limitations depending on your pro
On Feb 11, 7:59 pm, Graham Dumpleton
wrote:
> On Feb 11, 8:50 pm, Robin wrote:
>
>
>
> > Hi,
>
> > I am building some computational web services using soaplib. This
> > creates a WSGI application.
>
> > However, since some of these services are computationally intensive,
> > and may be long runni
2009/2/12 alex goretoy :
> GAE (Google App Engine) uses WSGI for webapps. You don't have to overhead of
> managing a server and all it's services this way as well. Just manage dns
> entries. Although, there are limitations depending on your project needs of
> what libs you need to use.
GAE is not
GAE (Google App Engine) uses WSGI for webapps. You don't have to overhead of
managing a server and all it's services this way as well. Just manage dns
entries. Although, there are limitations depending on your project needs of
what libs you need to use.
appengine.google.com
-Alex Goretoy
http://w
On Feb 11, 8:50 pm, Robin wrote:
> Hi,
>
> I am building some computational web services using soaplib. This
> creates a WSGI application.
>
> However, since some of these services are computationally intensive,
> and may be long running, I was looking for a way to use multiple
> processes. I thou
Robin wrote:
On Feb 11, 3:46 pm, Robin Becker wrote:
well the flup server for fast cgi supports forking if the server is declared as
an external process in apache. Then the top level of the flup process handles
each request and passes it off to a forked worker. I cannot recall exactly, but
I be
On Feb 11, 3:46 pm, Robin Becker wrote:
> well the flup server for fast cgi supports forking if the server is declared
> as
> an external process in apache. Then the top level of the flup process handles
> each request and passes it off to a forked worker. I cannot recall exactly,
> but
> I beli
On 2009-02-11 16:16, Diez B. Roggisch wrote:
> Robin wrote:
>
>> On Feb 11, 1:28 pm, Robin wrote:
>>> On Feb 11, 12:10 pm, Robin Becker wrote:
>>>
We've used forked fastcgi (flup) with success as that decouples the
wsgi process (in our case django) from the main server (in our case
>>>
Robin wrote:
..
Yes - I've done something very similar with ajp-wsgi (from the author
of flup; and which incidently performs very well works really nicely)
to go from apache -> wsgi. But the issue I'm asking about here is to
have multiple WSGI processes - ie to allow concurrent execution
Robin wrote:
> On Feb 11, 1:28 pm, Robin wrote:
>> On Feb 11, 12:10 pm, Robin Becker wrote:
>>
>> > We've used forked fastcgi (flup) with success as that decouples the
>> > wsgi process (in our case django) from the main server (in our case
>> > apache). Our reasons for doing that were to allow
On Feb 11, 1:28 pm, Robin wrote:
> On Feb 11, 12:10 pm, Robin Becker wrote:
>
> > We've used forked fastcgi (flup) with success as that decouples the wsgi
> > process
> > (in our case django) from the main server (in our case apache). Our reasons
> > for
> > doing that were to allow the backend
On Feb 11, 12:10 pm, Robin Becker wrote:
> We've used forked fastcgi (flup) with success as that decouples the wsgi
> process
> (in our case django) from the main server (in our case apache). Our reasons
> for
> doing that were to allow the backend to use modern pythons without having to
> upgra
Robin wrote:
Hi,
I am building some computational web services using soaplib. This
creates a WSGI application.
However, since some of these services are computationally intensive,
and may be long running, I was looking for a way to use multiple
processes. I thought about using multiprocessing.P
Hi,
I am building some computational web services using soaplib. This
creates a WSGI application.
However, since some of these services are computationally intensive,
and may be long running, I was looking for a way to use multiple
processes. I thought about using multiprocessing.Process manually
17 matches
Mail list logo
