This is not needed and we can manage with session store, but developpers must be informed not to use static attributes, given that they are shared between server instances. If not, developments that works locally may not in production context.
On 20 avr, 20:36, Nick Rudnik <[email protected]> wrote: > Why would this be needed? The session implementation stores its data outside > of a specific jvm so every instance has access to all sessions. It is a very > excellent design decision not to have to connect a user to a single instance > for the life of a session. Instances can come and go as they please without > affecting any existing sessions. -- 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 [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-java?hl=en.
