Is there a way to partially choose which operations to be performed when server-side processing is turned on. Eg: when turned on, only do paging and sorting on server side, but do the text filtering on client side, etc.
No - it is an all or nothing. They are all intrinsically linked really, which is why they can't be separated. You need to full set of data to do complete filtering, sorting or paging.
There is a scenario in which this might be useful. If you wanted to allow to load let's say 100 sorted values using server-side sorting, but then you wanted the filters to only be applied to those 100 values. I don't want the filters to be applied to all the data available on the server. I know I can just refetch the 100 values server-side and filter them then but it seems silly when all the data to filter is already available on the client.
Does that assume that the 100 values loaded is the complete data set? If not, then how would this cope with the fact that the 101st record might be shown after filtering, but all the records already loaded don't meet the filtering requirements - so the user would be shown "no records" if only filtering on the client-side.
I can see that this could be useful in some cases, but as I mentioned back in 2010, server-side processing is an all or nothing thing - either all of the processing is done at the server-side, or it is all done on the client-side. I think the potential for things going badly wrong with a mix of the two is quite great!
Replies
Allan
I can see that this could be useful in some cases, but as I mentioned back in 2010, server-side processing is an all or nothing thing - either all of the processing is done at the server-side, or it is all done on the client-side. I think the potential for things going badly wrong with a mix of the two is quite great!
Allan