session timeout feature description

Hugh Brock hbrock at redhat.com
Fri Jul 27 14:43:27 UTC 2012


Here is the agreed feature description for session timeouts, captured
from freenode/#aeolus:

There is an admin setting for session time in a config file, and...

<jayg> then we check after that time to ask if they are there

(This could mean "pop up a javascript warning)

<jayg> if no response after 30 seconds, log them out
<jayg> feature described

<hewbrocca> And
<hewbrocca> what resets the timer?
<hewbrocca> Do we have a way to differentiate backbone refreshes from
real
            user requests?  [11:25]
<matty_dubs> Non-Backbone activity == "activity"? Is that fair?
<jayg> a page refresh resets, I would think - or, clicking 'yes, I am
still
       here'

Seems to me we would do this in two stages:

1. Implement the timeout itself, ignoring backbone requests and
reading the desired time before session expiration from a system
configuration setting

2. Implement a "warning, you're about to timeout" dialog. This could
be entirely client-side, or it could be a backbone request to the
server for time-before-expiration

Is this sufficient?

--Hugh

-- 
== Hugh Brock, hbrock at redhat.com                                   ==
== Engineering Manager, Cloud BU                                   ==
== Aeolus Project: Manage virtual infrastructure across clouds.    ==
== http://aeolusproject.org                                        ==

"I know that you believe you understand what you think I said, but I’m
not sure you realize that what you heard is not what I meant."
--Robert McCloskey



More information about the aeolus-devel mailing list