In my opinion this can be performed when the model records change after querying jsonp, but needs not to be recalculated on every change in filtering/selection, so it shouldn't affect performances. At least I expect it to be "hidden" inside initial jsonp loading process with ajax spinner icon, so the user won't notice any performance difference.
In my opinion this can be performed when the model records change after querying jsonp, but needs not to be recalculated on every change in filtering/selection, so it shouldn't affect performances. At least I expect it to be "hidden" inside initial jsonp loading process with ajax spinner icon, so the user won't notice any performance difference.