I think this forum message captures my experience; http://groups.google.com/group/google-appengine-java/browse_thread/thread/fbf9ba7d3363c4aa/3f31bd5573f79b0b?lnk=gst&q=unload#3f31bd5573f79b0b
On Fri, Oct 9, 2009 at 12:07 PM, Rickard Öberg <[email protected]> wrote: > On 2009-10-09 12.03, Niclas Hedhman wrote: >> >> This means that the Qi4j Runtime is initialized a lot, which is an >> expensive operation. Somewhere down the line, I'll try to fix up the >> "model serialization" so that the main part of the initialization is >> skipped (significant fast startup) and once that is done, we can look >> at supporting storing/loading that model into the Google low-level >> store. > > And there's no way to keep the instance going between servlet startups? You > are actually supposed to take the whole app up/down all the time? > >> Then add to that, that servlets are not allowed to be 'processing' >> (not sure if thread creation is prohibited altogether, or it is just >> that the whole instance is killed) in the background and one can't >> have 'services' on Google's infra, I think Google AppEngine is fairly >> restricted, although really easy to use. > > Sounds close to useless to me... > > /Rickard > > _______________________________________________ > qi4j-dev mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/qi4j-dev > -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
