On 17 Mar 2006, at 15:00, James Cicenia wrote:
Hello -
I just implemented a "branded" version of our app. Basically this
means that the login in screen and graphics, some contact info,
etc., is triggered by the subdomain. This works great... HOWEVER...
If a person uses an old expired ses
James Cicenia schrieb:
Hello -
I just implemented a "branded" version of our app. Basically this
means that the login in screen and graphics, some contact info, etc.,
is triggered by the subdomain. This works great... HOWEVER...
If a person uses an old expired session... instead of being
Hello -
I just implemented a "branded" version of our app. Basically this
means that the login in screen and graphics, some contact info, etc.,
is triggered by the subdomain. This works great... HOWEVER...
If a person uses an old expired session... instead of being
redirected to a new ses
Another more complicated but cool ;-) approach would be to register
for WOSession's SessionDidTimeOutNotification, serialize the session
to persistent store (like a database), then override WOApplication's
handleSessionRestorationErrorInContext to reload the saved session.
You'd still have
Hello Norberto;
One way to do this is to add some code to your WO page which causes a
java timer to periodically fire at about half the session timeout.
This javascript should invoke a URL with the wosid from a direct
action. This has the end effect of keeping the session alive as long
I want to build an application where the users should not "time out";
ideally, they log in, and don't log out until the end of the day. The
application is for a small number of users (<50) submitting data.
What is the best way to allow users to open an application/web page
and stay "connect
