I guess ideally they should be able to submit from either but if that opens the app up to double submission than the most recent is fine as long as I have a way to handle the old form gracefully as far as user experience is concerned. I'm open to ideas.
On Sep 15, 4:51 pm, Anthony <abasta...@gmail.com> wrote: > Actually, now that I think about it, by default, web2py sessions don't > expire (except that the browser will expire the cookie at the end of the > browser session). There is an auth setting that expires logins, but if your > form page requires a login and the login had expired, I would expect the > user to get redirected to the login page instead of the form page simply > reloading. If you're using something like sessions2trash.py to expire > sessions, that could cause the session to expire (i.e., get deleted) on the > server side. > > Regardless of whether there's a session expiration problem, there could also > be a problem with opening the form in multiple tabs/windows. I suppose there > are workarounds in that case, but it depends on what you want to happen -- > should the user be allowed to submit the form from any and all open windows, > just the first window, just the most recent window (which is the default > behavior)? > > Anthony > > > > > > > > On Thursday, September 15, 2011 2:36:30 PM UTC-4, Lennon wrote: > > > So in that case it looks to me like web2py's timeout defaults to 3600 > > seconds (1 hour). > > > If a user had a form opened for over an hour and then attempted to > > submit the form, would that cause the form to be returned without > > errors just like the double form window would cause? > > > If so, that's probably what was happening as that seems much more > > likely than having two form windows open. > > > If that is the case, starting a JS timer on each page that alerted and > > redirected after an hour would solve this problem correct? > > > On Sep 15, 2:14 pm, Anthony <abas...@gmail.com> wrote: > > > On Thursday, September 15, 2011 2:03:24 PM UTC-4, Lennon wrote: > > > > > In that case does anybody have any ideas about how to gracefully > > > > handle this Session problem without removing session from > > > > form.accepts? > > > > > Anthony suggested having a javascript pop-up when the session times > > > > out but don't web2py sessions not timeout while the browser remains > > > > open be default? > > > > If the browser is open but not sending any requests back to the server, > > the > > > server has no way of knowing it is still open, so the session can still > > time > > > out. > > > > Anthony
