On Mon, Sep 19, 2011 at 10:16 AM, HARISH S.C wrote:
> Hi,
> I would like to clarify some basic doubts. I am trying to port an
> existing app into google app engine .
>
> 1. When I have more than 1 servlet, it ll be executed in different
> thread in a single JVM or else how it will be executed ?
Hi,
I would like to clarify some basic doubts. I am trying to port an
existing app into google app engine .
1. When I have more than 1 servlet, it ll be executed in different
thread in a single JVM or else how it will be executed ?
2. Is there any workaround to eliminate threading?
3. Can we c
Howdy,
With the new pricing being instance based, rather than CPU time based, it
seems more important to know how the instances themselves work.
How many concurrent requests can a single Java GAE instance service?
Important if the app is doing any long polling on the client.
thanks
-- James
I am doing a project where I will try to optimize google engine by using
multi-core cpus. So, now i am doing a research how the low API works in
order to find out if such an optimization is possible.
On Fri, Mar 5, 2010 at 7:20 PM, John Patterson wrote:
> Basically each request is a thread in app
Basically each request is a thread in app engine. There are a couple
of ways to create multiple requests:
task queues - when you don't need to wait for a response
async url fetch - when you do need the results of your threads
On 5 Mar 2010, at 23:54, Marios wrote:
Hello there,
I've just re
Hello there,
I've just read the documentation on Google App Engine and I realised
that you cannot create any threads in an application. You can only use
the main one which is created automatically with any runnable java
program.
I am wondering if there is the possibility to create threads using the
