On Sep 8, 2:58 pm, David Given <[email protected]> wrote:
> Adligo wrote:
> > I mentioned is stored as a Session Attribute. I assume that the app
> > engine must be
> > keeping the Session in a location that can be accessed by all
> > threads.
>
> I'm afraid not!
>
> The *only* mechanism for communicating between requests is, AFAIK (and
> if I'm wrong someone please correct me), memcache or the datastore.
>
Actually, you can also use the URLFetch service to make callbacks to
your application, thereby providing a thread a way to talk to another
thread.
This is used to good effect to parallelize queries in the asynctools
project, http://code.google.com/p/asynctools/.
<blatant promotion of self interest>
Unfortunately, the Java API does not support async URLFetch like
the Python API.
Please go vote for async URLFetch in Java here...
http://code.google.com/p/googleappengine/issues/detail?id=1899&q=emorning&colspec=ID%20Type%20Status%20Priority%20Stars%20Owner%20Summary%20Log%20Component
</blatant promotion of self interest>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---
