Logout / Re-login - why / how? Timeout?
Hi,
What causes Nirvana to log me out? I am currently using NirvanaHQ across 3 platforms: Mac OS X, Win XP and Droid. I've used it with Firefox, Chrome and Safari and, occasionally, when I fire up Nirvana I find that I've been logged out. This is not a huge deal on the Mac or PC but it's much more annoying on the Droid since it takes more effort to type a password (and everything is slower on a mobile browser).
So I'm trying to understand what causes the logout so I can better control this behavior. Does it have anything to do with concurrent use? I definitely try never to use Nirvana on two browsers at the same time but I may leave it on in one computer and later on access it in a different computer. Is that what causes the logouts?
I believe this topic has been brought up before but I couldn't find it this morning so apologies for that and please merge the two discussions if that's true.
As a sidenote, 2 weeks into my trial of NirvanaHQ and I absolutely love it. Great job guys!
Cheers, -Alex
2 Posted by James on 23 Aug, 2010 06:06 PM
I'm experiencing this too, and it's especially frustrating to encounter the login prompt on the iPhone. As great as the webapp is, I'm going to have to find another gtd solution if the mobile interface does not improve.
Support Staff 3 Posted by Elbert McLaughlin on 23 Aug, 2010 06:26 PM
Hi Folks - Thanks for bringing this to our attention. I thought we'd nipped this problem in the bud a few weeks back, but I guess not. Will have someone here have a look into why sessions are expiring so quickly.
Thanks for your patience while we address this...
Elbert
4 Posted by Alex on 27 Aug, 2010 02:15 PM
I'm not sure it's exactly a problem. It's the way you guys handle concurrent use to avoid potential conflicts. For example, logouts seem to happen when I leave Nirvana open in another browser/PC and try to fire it up somewhere else. I haven't fully tested all the conditions that trigger logout but that seems to be the main one.
I suppose that is better than corruption of data. I just wanted to understand how it works and how to prevent it from happening (especially, as I mentioned, when I need to access it on the mobile).
I don't know if there's a more elegant way to handle this that is safe at the same time. This might be particularly relevant (or not) when the local app gets released.
Support Staff 5 Posted by Elbert McLaughlin on 30 Aug, 2010 04:53 PM
Hi All -
We bumped the session timeout to 2 weeks, so you should start seeing the annoying timeout alerts a lot less often.
@Alex - it's nothing all that sophisticated really! It was just an unusually short session timeout length that was put in place while we were doing rapid deployments a few weeks ago. Needed to make sure folks weren't lingering on a stale version. Somehow we hadn't restored the session timeouts to something more sane.
In the near future this will no longer be an issue, as when we move to the html5 code base all access to Nirvana (behind the scenes) will go through the state-less (and cookie-less) API.
Thanks for hanging in there while we work out these kinks!