Performance Considerations (Commit)

In some cases, content developers require setting the bookmark or other SetValue on a page-turn by page-turn basis (or even more frequently) to monitor and capture user progress through the course. If a Commit ("") is called with each page turn, the resulting content:

is slow to operate
places an undue overhead on Skillport by forwarding a TCP/IP data update and request against Skillport
requires a response before the content frameset is free to respond to user interaction

It is unacceptable for a content developer to run the Commit this frequently, and Skillport does not support such content. In general, the Commit call should happen once every 10-15 minutes, or at the completion of a module/lesson point, providing that the lesson point is every 10-15 minutes.

The Finish command does an implied Commit command, so you do not have to run the Commit call.