You need to enable sessions in the appengine-web.xml,

<!-- HTTP Sessions are disabled by default. To enable HTTP sessions 
specify: -->
<sessions-enabled>true</sessions-enabled>

<!-- It's possible to reduce request latency by configuring your 
application 
to asynchronously write HTTP session data to the datastore: -->

<async-session-persistence enabled="true" />

<!-- With this feature enabled, there is a very small chance your app will 
see stale session data. For details, see 
http://code.google.com/appengine/docs/java/config/appconfig.html#Enabling_Sessions
 
-->



On Wednesday, July 27, 2011 at 6:33:19 PM UTC-4, Sateesh wrote:
>
> Hi 
>
> Is there a way that i can use Servlet Context on Appengine. 
> Here is our scenario 
>
> We have GWT application 
> Client call a server method to get the xml data (which is around 5 mb) 
> Server method will prepare a map with a unique key and value as in 
> progress 
> Server will send request to another server (SERVER2) with key as 
> parameter 
> SERVER2 sends SUCCESS message after spanning a thread to fetch xml 
> from data store. 
> Client will use polling mechanism to see the status for this request 
> in Servelet context stored map 
> SEVER2 later post back the data to a servlet which will update the 
> value of a map in ServletContext 
> Client will pickup this and use in rendering 
>
> It seems that i am unable to store data in to Servlet Context in 
> Appengine. 
> In my case mem cache is not the right choice as my data is huge. 
> Please suggest how to over come this situation 
>
> Thanks 
> Sateesh

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/1e2f4e61-2ed2-4651-963e-dbe2cdb055f1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to