Hi!
We try to use RadEditor in our site pages, where group of students able to edit same data. We need to implement some concurrency mechanism. We need to be sure, that previously edited data will be used for next editing and that user will know if someone already changed some Editor data during current user editing.
Is there exists some standard realization or best practices for such workflow?
Now we try to make it using client events in two steps:
1. Update data from server on start editing
It used OnFocus event, disable control and calls server-side checking of conflicts, then enable it after update control data from server.
2. Update data at server on finish editing
It used OnBlur event and send data to server for update
We already have problems with such realization. For example, on page loading we have OnFocus event fired by each Control (it's standard RadEditor behaviour) and it causes additional not necessary requests to server.
What would be a solution for this cases?
We try to use RadEditor in our site pages, where group of students able to edit same data. We need to implement some concurrency mechanism. We need to be sure, that previously edited data will be used for next editing and that user will know if someone already changed some Editor data during current user editing.
Is there exists some standard realization or best practices for such workflow?
Now we try to make it using client events in two steps:
1. Update data from server on start editing
It used OnFocus event, disable control and calls server-side checking of conflicts, then enable it after update control data from server.
2. Update data at server on finish editing
It used OnBlur event and send data to server for update
We already have problems with such realization. For example, on page loading we have OnFocus event fired by each Control (it's standard RadEditor behaviour) and it causes additional not necessary requests to server.
What would be a solution for this cases?