Hi Michael,
many thanks for the help! Yes I think I am using the wrong way.
What I need is a long running request "main" that execute some code
server side. At some time the "main" request need client values.
I have thinked to use a second request that take the work to fetch
a client value and once again on a request, it give the value to the
"main" request that then will continue to execute. Because the
"main" request survive more "fetch" requests, the session is not
updated ad expected.
Do you think that channel api can help me for this?
On 05/10/2012 11:22 PM, Michael Hermus wrote:
It is definitely NOT written until the end of the request. You cannot use the
session object that way. Memcache would be your best alternative, but it is
possible you are attempting to implement a flawed pattern.
On Thursday, May 10, 2012 5:12:01 PM UTC-4, Davide wrote:
Hi,
is possible that session is not replicated until the end of the http request
is reached? How is possible to replicate DURING the http request?
I am on the wrong way?
--
You received this message because you are subscribed to the Google Groups "Google
App Engine" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/kkGvdz2IcZQJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.
--
You received this message because you are subscribed to the Google Groups "Google
App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.
