In terms of the dhtmlxDataProcessor, looks like you only sa

In terms of the dhtmlxDataProcessor, looks like you
only save one record at a time, which might be expensive if the user have
multiple records.

The latest code of
dhtmlxDataProcessor supports sending all of data in single instance, but it has
only sample of server code, and handling multiple rows in one request can be
more complex task than only one row per request, as current solution does. (
Current solution was build with concept of immediately updating row after
change, updating one row per request work quite well for such task ).