The AutoSave functionality, or a manual equivalent, triggers an appropriate client-side save of the user's modifications immediately before a postback. In most cases this is all that is necessary.

However, if user sessions are expected to include substantial edits and continue for an extended period, it may be appropriate to also save the user modifications to the server at regular intervals.

If the SaveInterval property is set to a non-zero positive value, the client-side editor will create a client-side timer and check for modifications on each tick. If the HTML has been modified, the client-side editor will:

1. Call Save(), which converts to XHTML if appropriate, and clears the modified flag
2. Trigger an asyncronous postback

To handle the asyncronous postback, attach a handler to the Save Event. See the documentation on the Save Event for more information.

If the SaveInterval is set to 0, the default, no timer is created on the client.

Because asyncronous postbacks take time, the value must be set to at least 3 seconds, if not set to 0. And since frequent postbacks create a heavy load on the server, the highest value possible is recommended.