Google and the apple docs are surprisingly silent about this.
I have an application where almost all access is for members only,
thus requiring login, but almost all pages are accessed by direct
action. Of course if I set "refuse new sessions" because I've deployed
a new version in another instance, it does nothing because new users
connect via direct action and get a new session.
I'm wondering what is the standard way of handling this? Should I test
for isRefusingNewSessions() and hasSession() and redirect the visitor
to the same URL, hoping that eventually they will get another
instance? Is there a better way?
Regards
Thomas
This archive was generated by hypermail 2.0.0 : Sun Feb 03 2008 - 19:35:15 EST