Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-45757

SCORM packages & session timeouts


    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • None
    • 2.6.3
    • SCORM
    • None

      Some SCORM packages will have a user browsing through information for hours, without hitting the server. This means the user's session has timed out by the time they go to take their next action and can result in loss of data / completion steps.

      To work around this, we implemented a "keep-alive" ticker. Essentially SCORM windows hit the server every 15 minutes to refresh the session and keep it alive.

      This isn't entirely straightforward, as timeouts are there (amongst other reasons) for when users leave the screen unattended / etc.
      This circumvents this security measure - which not everyone would agree with.

      Thought I'd open a ticket to see what people thought, as I am not entirely comfortable with the approach we were asked to take.

      See MDL-4433

            danmarsden Dan Marsden
            skylarkelty Skylar Kelty
            0 Vote for this issue
            3 Start watching this issue


                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.