ProActive Scheduler

Scheduler frontend should attribute session to user in order to avoid growing size of user identification list

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 1.0, 2.0 Technology Preview
  • Fix Version/s: 2.0 Technology Preview
  • Component/s: scheduler-Core
  • Description:
    A session mechanism should be used to drop user after a given time

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Jean-Luc Scheefer added a comment - 28/May/09 3:28 PM
Each user have a defined session (the time of the session can be set in the PASchedulerProperties.xml file)
- If no activity is detected for a user and the time of the session runs out of time, the user and the associated session is removed from Scheduler.
- If the user register for listeners, the session becomes infinite as it is possible to check if the user is dead or alive.
        When user disconnect from listening events, its session is set back.
Show
Jean-Luc Scheefer added a comment - 28/May/09 3:28 PM Each user have a defined session (the time of the session can be set in the PASchedulerProperties.xml file) - If no activity is detected for a user and the time of the session runs out of time, the user and the associated session is removed from Scheduler. - If the user register for listeners, the session becomes infinite as it is possible to check if the user is dead or alive.         When user disconnect from listening events, its session is set back.

People

Dates

  • Created:
    05/May/09 5:55 PM
    Updated:
    04/Nov/09 5:01 PM
    Resolved:
    28/May/09 3:28 PM
Atlassian JIRA (v4.1.1#522) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for ProAcrtive. Try JIRA - bug tracking software for your team.