Skip to content
This repository has been archived by the owner on Jun 30, 2018. It is now read-only.

IBM comment 1 on 2.2.8 Timeouts #448

Closed
mbgower opened this issue Oct 9, 2017 · 3 comments
Closed

IBM comment 1 on 2.2.8 Timeouts #448

mbgower opened this issue Oct 9, 2017 · 3 comments

Comments

@mbgower
Copy link
Contributor

mbgower commented Oct 9, 2017

"User inactivity" should likely be defined. For instance, does timing begin from a user login? What differences should be considered for server-side functionality versus client side?

@mbgower
Copy link
Contributor Author

mbgower commented Nov 7, 2017

Rachael, here's what you posted in our chat today. I'll look over and try to tweak...

User Inactivity: Any continuous period of time where no user actions occur that trigger tracked client or sever activity. The method of tracking will be determined by the web site or application and should be consistent with the way the site or application determines time outs.

@rachaelbradley
Copy link

Discussions at TPAC resulted in the following definition:

User Inactivity: Any continuous period of time where no user actions occurs. The method of tracking will be determined by the web site or application.

@awkawk
Copy link
Member

awkawk commented Dec 6, 2017

Finalized by WG 12/5

@awkawk awkawk closed this as completed Dec 6, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants