Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #4738
| References | <a843a6cd-c2dd-4fdc-a8db-1f687e775eb8@f31g2000pri.googlegroups.com> |
|---|---|
| Date | 2011-05-06 00:47 +1000 |
| Subject | Re: Need to solve the "Stateless HTTP" problem |
| From | Chris Angelico <rosuav@gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.1193.1304606853.9059.python-list@python.org> (permalink) |
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
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
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
csiph-web