[google-appengine] Re: App state issue - Calvin Spealman - com.googlegroups.google-appengine

9 messages in com.googlegroups.google-appengine[google-appengine] Re: App state issue

From	Sent On	Attachments
WanderingGAE	28 Jul 2008 07:29
Calvin Spealman	28 Jul 2008 07:39
Calvin Spealman	28 Jul 2008 08:00
Calvin Spealman	28 Jul 2008 08:11
WanderingGAE	28 Jul 2008 09:48
Matt Painter	29 Jul 2008 10:24
Calvin Spealman	29 Jul 2008 14:43
Philip Tenn	29 Jul 2008 18:17
Matthew Painter	30 Jul 2008 00:44

Subject:	[google-appengine] Re: App state issue
From:	Calvin Spealman (iron...@gmail.com)
Date:	07/29/2008 02:43:54 PM
List:	com.googlegroups.google-appengine

The pyc doesn't contain the results of any expressions, only the compiled bytecode. Any globals, for example, are still computed on each new load of the module, be it from py or pyc. However, if the process is cached the module will stay in memory and the globals and class attributes will stick around between requests.

On Tue, Jul 29, 2008 at 1:24 PM, Matt Painter <mjg...@matthewpainter.com> wrote:

In fact, after the first use of a module is compiled it is cached in a pyc, so any static variables on subsequent requests will have initial values of the first request values - kinda like mod_perl :o)

This can be great for picking up performance (compiling regular expressions anyone?), but just be aware that this can have some pretty funky wierd side effects if you are not expecting it!

On Jul 28, 5:58 pm, "Calvin Spealman" <iron...@gmail.com> wrote:

Yes.

On Mon, Jul 28, 2008 at 12:48 PM, WanderingGAE <Weri...@gmail.com> wrote:

Does that include requests from different users/ip's?

On Jul 28, 11:12 am, "Calvin Spealman" <iron...@gmail.com> wrote:

If you have a main function in your script, its all kept alive between requests. This is included in the appengine docs.