Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #4729 > unrolled thread

Need to solve the "Stateless HTTP" problem

Back to article view | Back to comp.lang.python

Contents

  Need to solve the "Stateless HTTP" problem Gnarlodious <gnarlodious@gmail.com> - 2011-05-05 07:22 -0700
    Re: Need to solve the "Stateless HTTP" problem garabik-news-2005-05@kassiopeia.juls.savba.sk - 2011-05-05 14:37 +0000
    Re: Need to solve the "Stateless HTTP" problem Chris Angelico <rosuav@gmail.com> - 2011-05-06 00:47 +1000
    Re: Need to solve the "Stateless HTTP" problem Ian Kelly <ian.g.kelly@gmail.com> - 2011-05-05 11:07 -0600

#4729 — Need to solve the "Stateless HTTP" problem

My scripting has grown to the point where the Apache server is a
problem. My Python websites run and quit, which means I need to save
data and recreate everything next page load. Bulky and slow. What is
the simplest solution?

I am running Py3 on OSX Server with Apache 2. Essentially I want
certain objects to be a "constantly running process" that may timeout
after some disuse. I suspect there are already systems for it. Please
advise in simple terms, I am not a professional.

-- Gnarlie

[toc] | [next] | [standalone]

#4736

Gnarlodious <gnarlodious@gmail.com> wrote:
> My scripting has grown to the point where the Apache server is a
> problem. My Python websites run and quit, which means I need to save
> data and recreate everything next page load. Bulky and slow. What is
> the simplest solution?

Karrigell?
-- 
 -----------------------------------------------------------
| Radovan Garabík http://kassiopeia.juls.savba.sk/~garabik/ |
| __..--^^^--..__    garabik @ kassiopeia.juls.savba.sk     |
 -----------------------------------------------------------
Antivirus alert: file .signature infected by signature virus.
Hi! I'm a signature virus! Copy me into your signature file to help me spread!

[toc] | [prev] | [next] | [standalone]

#4738

On Fri, May 6, 2011 at 12:22 AM, Gnarlodious <gnarlodious@gmail.com> wrote:
> My scripting has grown to the point where the Apache server is a
> problem. My Python websites run and quit, which means I need to save
> data and recreate everything next page load. Bulky and slow. What is
> the simplest solution?
>
> I am running Py3 on OSX Server with Apache 2. Essentially I want
> certain objects to be a "constantly running process" that may timeout
> after some disuse. I suspect there are already systems for it. Please
> advise in simple terms, I am not a professional.

Depending on how much of Apache's featureset you're using, it may be
easiest to set it aside altogether and just run a Python HTTP server.
Then you can maintain as much state as you like.

But if you're currently hosting multiple sites and distinguishing
between them using Host: headers (using NameVirtualHost), then you'd
have to change them all, which probably wouldn't be worthwhile.

Chris Angelico

[toc] | [prev] | [next] | [standalone]

#4766

On Thu, May 5, 2011 at 8:22 AM, Gnarlodious <gnarlodious@gmail.com> wrote:
> My scripting has grown to the point where the Apache server is a
> problem. My Python websites run and quit, which means I need to save
> data and recreate everything next page load. Bulky and slow. What is
> the simplest solution?
>
> I am running Py3 on OSX Server with Apache 2. Essentially I want
> certain objects to be a "constantly running process" that may timeout
> after some disuse. I suspect there are already systems for it. Please
> advise in simple terms, I am not a professional.

It sounds to me like you're currently running your Python scripts as
CGIs?  You should look into running your scripts via mod_wsgi in
daemon mode, which will do exactly what you are asking.  See here:

http://code.google.com/p/modwsgi/

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web