Hi Alexander,
Google also provides a servlet to help with deleting stale session
info. Have a look at this thread:
http://groups.google.com/group/google-appengine-java/browse_thread/thread/4f0d9af1c633d39a
Best regards,
Stefan
On 23 Nov., 18:06, Alexander Arendar alexander.aren...@gmail.com
Normally, session cookies are created non-persistent on the browser side,
but you could try to re-set the session cookie in a filter and use
Cookie.setMaxAge(int) to make it persistent, like lembas did with GWT in his
initial post.
For plain Servlet API it could look like:
String sessionId =
Hi Stephan,
Is that possible that a client had closed the browser and opens a new
browser and we can still identify the client using session cookies?
Thanks
Romesh
On Thu, May 27, 2010 at 10:42 PM, Stephan Hartmann hartm...@metamesh.dewrote:
Keep in mind that sessions managed by the servlet
Hi Keremonal,
As my practice I don't depend on Cookies for session management, because if
cookie is disabled at client browser then you will always get a new session
id and your data which was previously stored in session gets lost. As I
think _ahsession is a very good thing for session mgmt. The
Cookies are the most suitable thing for the remember me functionality best
works. Because sessions end with the end of browser window and cookies still
survive (if specified long life)
Romesh
On Thu, May 27, 2010 at 1:28 PM, lembas keremo...@gmail.com wrote:
thanks romesh. I was on vacation
Keep in mind that sessions managed by the servlet container expire after a
specific time of inactivity on the server side, so if a user comes back
after a while with his old session cookie, he will still get a new session.
According to the servlet spec, you can obtain this value with
