Re: [google-appengine] Session/user management approach for multiple servlets in GWT/GAE app

2011-07-08 Thread Stephen Johnson
I'm assuming this is on production not dev? Do you have true in your appengine-web.xml? Are you seeing the sessions persisted to the datastore in _ah_Session? Stephen On Fri, Jul 8, 2011 at 3:54 AM, Alex Dobjanschi wrote: > Hi, > I've been unsuccessful in sharing a piece of data (Account) betw

[google-appengine] Session/user management approach for multiple servlets in GWT/GAE app

2011-07-08 Thread Alex Dobjanschi
Hi, I've been unsuccessful in sharing a piece of data (Account) between multiple servlets (doing custom user management, not using UserService). I'm developing a GWT/GAE app, where multiple client services get implemented by different servlets. What's the best/good approach for this? Upon login/

Re: [google-appengine] Session User

2010-12-19 Thread Sarfaraz
Hi Wasfi, Use gaesessions. I am using this library and its very lightweight and robust. and can be used with webApps framework. it can be configured to use cookies, memcache and the datastore. read the advantages here : https://github.com/dound/gae-sessions and then follow the directions to ins

[google-appengine] Session User

2010-12-19 Thread Mohamed Wasfi
I am developing an app where I don't want to force the users to use google authentication or openID but just sign in with their basic e- mail addresses. I will create the login and logout pages myself. Can I get a suggestion on how to keep track of the current user in the session like what "user =

Re: [google-appengine] session user property not updated. weird bug?

2010-03-08 Thread Sümer Cip
Of course this approach is only valid if I can guarantee no subsequent put() operations will happen in a single request which in my case unlikely. Or is there a better generic approach you can suggest? On Mon, Mar 8, 2010 at 4:09 PM, Sümer Cip wrote: > Yes, exactly, I finally found the problem y

Re: [google-appengine] session user property not updated. weird bug?

2010-03-08 Thread Sümer Cip
Yes, exactly, I finally found the problem yesterday, gaeutlities session behaves different on each object. So how about this solution: I have a base handler class for all the handlers and what I added is to refresh the user param from the datastore for every __init__ function. How that sounds? cla

Re: [google-appengine] session user property not updated. weird bug?

2010-03-08 Thread Nick Johnson (Google)
Hi Sumer, You're storing an entity in the session, and unless the gaeutilities session object handles this specially, this results in it pickling the 'user' entity and storing it in the session. Calling .put() on the user object will update the datastore with the new value, but won't change the pi

[google-appengine] session user property not updated. weird bug?

2010-03-06 Thread Sumer Cip
Hi all, Below is the code code I am using in my tests to update a reference tied to my session, the session object I use if from gaeutilities (wrapped it a little). I put a reference object in the session and all working fine. if not self.Session.user: user = scMember.all().fi