Hello Tonny,
you are right of cause, that one could overwrite complete function in all $.ajax requests with respect of $.jgrid.ajaxOptions, ajaxEditOptions or ajaxso parameters. But on the other side if somebody does so, he’ll receive problem of using internal jqGrid structures. In complete function inside of createEl in grid.common.js for example one needs use options and other variable in the scope.
The main idea of my suggestion is very easy. With respect of custom serialization/deserialization functions one could change paradigm of jqGrid usage on the side of backend services. Currently one has to provide on the backend server services providing data for jqGrid in a special format prepared for jqGrid. If you allow to use custom serialization and destabilization functions, if would be possible use many existing backend services and convert data for jqGrid before and after $.ajax requests. The conversion can de done on the client side, without any additional requirement to the backend! It could be important for lot of scenarios of jqGrid usage.
Functions serializeGridData, serializeRowData, serializeEditData from v.3.6 provide serialization, but I found no deserialization functions. There are exists also errorfunc, errorTextFormat, which are very useful for decode error messages provided by server.
Why not provide functions like deserializeGridData etc., which could convert data send from server (responseText) to format needed for jqGrid? For example, for conversion from JSON format to HTML fragment (…) like in the case of dataUrl?
Best regards
Oleg