Hi Sergio,
I've been playing around with Google App Engine's recent Java support.
They are pretty restrictive -- you can't spawn new threads (new Thread
() isn't permitted by their security manager).
The restrictions make lots sense in terms of billing and performance
management, but since they already limit CPU time, I see no harm to
them in trying to regain some limited concurrency within the local
scope of a single request, if just for the fun of it :)
That's how I came by your library -- searched Twitter for "green
threads".
I tried to deploy a modified pingpong-with-local-actors sample in GAE
SDK's local server, but ran against GreenMessageDispatcher, trying to
create a new selector thread.
My question: since the selector thread is essentially a "main loop",
would it make any sense to pull its functionality to the main thread?
that is, create a topology, spawn actors, but defer the OnSpawn event
handling to when the main loop starts up.
This way, a single request to a GAE application can spin up lots of
actors for a short duration.
Does this make any sense?
Thanks,
-Nadav.
