If an application has both threadsafe and sessions-enabled set to true, then
will calls to the session API block so that one frontend instance can only
execute one such call at a time when there are several threads running?
--
You received this message because you are subscribed to the Google
The session API is thread safe. Hence there is no need to single thread
requests.
On Sunday, September 4, 2011, Anders blabl...@gmail.com wrote:
If an application has both threadsafe and sessions-enabled set to true,
then will calls to the session API block so that one frontend instance can
only
Ok, good. Thanks.
--
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/-/9BHMnXPUZJkJ.
To post to this group, send email to
And threadsafe in this case means that the Session API can handle several
calls to it simultaneously from the same frontend instance? Or will it block
so that only one thread at a time can access the Session API? Because if it
blocks then it will become a bottleneck since the threads then have
Same problem here with sessions. 100% reproducible.
Please star issue.
http://code.google.com/p/googleappengine/issues/detail?id=4224
On Aug 10, 7:48 am, Yoshihito Yamanaka jfox4...@gmail.com wrote:
No, but other pages are using session.
(Maybe 500 error page is using session. so this
Do not use the method Text.toString(), use Text.getValue() instead.
--
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
Three months ago instances were limited to 10 concurrent requests but
apparently this restriction will be completely removed (may already be
removed) and the CPU usage of your app will be the sole determinant of
concurrency. So if your app handles requests very efficiently it will
handle a
