Not really. You shouldn't depend on App Engine instances to stay alive since we will tear them down and start them up as needed. What is it that you are doing that you can't do with Memcache?
An alternate implementation could be to use Backends to maintain a long lived data object cache, but this is arguably more expensive engineering-wise than just using memcache. Ikai Lan Developer Programs Engineer, Google App Engine Blog: http://googleappengine.blogspot.com Twitter: http://twitter.com/app_engine Reddit: http://www.reddit.com/r/appengine On Sun, Jun 19, 2011 at 4:47 AM, Inderjeet Singh <inder...@gmail.com> wrote: > Hi, > > I recently upgraded to the paid version of Google App Engine since I wanted > to keep my application instance always running. However, I now see that > App-Engine creates 3 instances by default. This forces me to use a solution > like Memcache which I am not yet ready to do. Is there a way to limit the > number of instances to just 1. > > Thanks > Inder > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine-java/-/BFpppoff134J. > To post to this group, send email to > google-appengine-java@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
