1 Answer, 1 is accepted
0
Hello Robert,
The concurrency control should happen on the database level. Concurrency control cannot be changed on the client side.
For examples if there are two users that retrieved a specific record.
They both modify their local copies and submit them in different time, inside your update action method you will receive the updated record and you need to decide there how concurrency will be resolved. When the second one tries to update you can throw an exception that the record was modified :
http://blogs.telerik.com/kendoui/posts/13-08-29/handling-server-side-validation-errors-in-your-kendo-ui-grid
Kind Regards,
Petur Subev
Telerik
The concurrency control should happen on the database level. Concurrency control cannot be changed on the client side.
For examples if there are two users that retrieved a specific record.
They both modify their local copies and submit them in different time, inside your update action method you will receive the updated record and you need to decide there how concurrency will be resolved. When the second one tries to update you can throw an exception that the record was modified :
http://blogs.telerik.com/kendoui/posts/13-08-29/handling-server-side-validation-errors-in-your-kendo-ui-grid
Kind Regards,
Petur Subev
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.