Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!feeder.news-service.com!newsfeed.xs4all.nl!newsfeed6.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.004 X-Spam-Evidence: '*H*': 0.99; '*S*': 0.00; 'subject:" ': 0.03; '(using': 0.05; 'scripting': 0.05; 'python': 0.07; 'essentially': 0.12; 'am,': 0.14; 'wrote:': 0.14; '12:22': 0.16; 'osx': 0.16; 'py3': 0.16; 'simplest': 0.16; 'solution?': 0.16; 'terms,': 0.16; 'timeout': 0.16; 'using,': 0.16; "wouldn't": 0.18; 'header:In- Reply-To:1': 0.22; 'received:209.85.214.174': 0.23; 'received :mail-iw0-f174.google.com': 0.23; 'objects': 0.24; 'apache': 0.25; 'easiest': 0.25; 'subject:problem': 0.25; 'suspect': 0.25; 'chris': 0.27; 'message-id:@mail.gmail.com': 0.28; 'server': 0.29; 'fri,': 0.29; 'like.': 0.29; 'probably': 0.30; 'server.': 0.31; 'recreate': 0.31; 'it.': 0.31; 'all,': 0.31; 'to:addr:python- list': 0.32; 'headers': 0.33; 'page': 0.33; 'using': 0.34; 'certain': 0.34; 'change': 0.34; 'there': 0.35; 'point': 0.35; 'running': 0.36; 'problem.': 0.36; 'data': 0.37; 'some': 0.37; 'received:209.85': 0.37; 'run': 0.37; 'http': 0.38; 'received:google.com': 0.38; 'but': 0.38; 'received:209.85.214': 0.39; 'set': 0.39; 'to:addr:python.org': 0.39; 'where': 0.39; 'received:209': 0.39; 'how': 0.39; 'hosting': 0.39; 'aside': 0.40; 'header:Received:5': 0.40; 'simple': 0.60; '2011': 0.62; 'sites': 0.62; 'websites': 0.77; 'slow.': 0.84 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=OSKROWgcbZRYQt8uOQZx0iO3MU2Gbat+UAG5pfEBFoU=; b=o4RKkWHAP3cDfiADYBmAvmglieg76zEZvvgUvXPT838KwBRJP3iOxTUO5QD19+QOiP 8kcilOXAypQTQ9JBs7KXoYg5o1LLxFEvCGrLI4zmvaS/8QN2Th0HSc+HsO6U8ECiAkHz bqZIt41u0rTiRYiqtpSdnNfeEoMs6zWCaPmb4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=I1LrRLWAD5zc4rV4FuIDDqiPUUp1z6t/9Rn5Ipi6YDvpbP2BTm9ZbU2KL2gIVelyWZ XppZlXSKyZ59nWMUsvBroghuiCuiU8+t/WQsUhjUfkYAf3dQhbuUQmpWrV17ZPNG51Uk 0OTY3NetofzmECnHtyCM3IWpV8V1cN0LZneVo= MIME-Version: 1.0 In-Reply-To: References: Date: Fri, 6 May 2011 00:47:30 +1000 Subject: Re: Need to solve the "Stateless HTTP" problem From: Chris Angelico To: python-list@python.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 20 NNTP-Posting-Host: 82.94.164.166 X-Trace: 1304606855 news.xs4all.nl 81482 [::ffff:82.94.164.166]:35563 X-Complaints-To: abuse@xs4all.nl Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:4738 On Fri, May 6, 2011 at 12:22 AM, Gnarlodious 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