FORCED_COMMIT_TIME value of 60000 (60k)

Hi Ashley,

Thanks.  That has explained a lot of what is going on (despite being related to Studio '09).

I've checked the lms.js file that SL2 packages up with the course and found:

setInterval("ForceCommit()", 600000);

So,

1. SL2 uses a 600000ms (10 minute) interval rather than a 60000ms (1 minute interval)
2. SL2 is NOT using the value in configuration.js despite it making sense to do so.
3. The value is hardcoded in the code rather than in configuration.js.
4. There is no option (such as setting the value to 0 like the comment suggests in configuration.js) to switch off auto-committing.  One would have to comment out the line of code in lms.js.

I can propose a change request for the developers to:

1. Amend configuration.js to set the value of FORCED_COMMIT_TIME to 600000 (10 minutes) in line with a 10 minute interval currently hard coded in lms.js.
2. Amend lms.js to make use of the FORCED_COMMIT_TIME rather than hard coding the value.

This will make it a lot easier (and a lot less misleading) to course builders who wish to customise the forced commit time.

Thanks,

Chris