Hi there
I've tried accessing the information via the documentation (and a Google search) but can't find a concise answer.
What are the differences between using Ajax VS Server binding / editing.
It appears as though they pretty much support the same feature set. Is it just that server binding forces a page reload? I note that there are some client-side events that are not raised when server binding is used.
Can you please clarify the pros and cons of Ajax VS Server binding / editing?
Thanks,
Paul.
I've tried accessing the information via the documentation (and a Google search) but can't find a concise answer.
What are the differences between using Ajax VS Server binding / editing.
It appears as though they pretty much support the same feature set. Is it just that server binding forces a page reload? I note that there are some client-side events that are not raised when server binding is used.
Can you please clarify the pros and cons of Ajax VS Server binding / editing?
Thanks,
Paul.
3 Answers, 1 is accepted
0
Hello Paul,
Basically Ajax is using Ajax requests when you page/sort/group/filter also Ajax request when you add/update/delete records.
In Server mode each operation is doing a GET or POST request to the server and it refreshes the whole page. However when using server binding you have better search indexing (like google etc) you can give url-s which represent the current Grid set.
In Ajax mode the user interaction will be smoother and the server will not have to re-create the whole page - which makes it the lightweight scenario.
Kind regards,
Petur Subev
the Telerik team
Basically Ajax is using Ajax requests when you page/sort/group/filter also Ajax request when you add/update/delete records.
In Server mode each operation is doing a GET or POST request to the server and it refreshes the whole page. However when using server binding you have better search indexing (like google etc) you can give url-s which represent the current Grid set.
In Ajax mode the user interaction will be smoother and the server will not have to re-create the whole page - which makes it the lightweight scenario.
Kind regards,
Petur Subev
the Telerik team
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
0
Paul
Top achievements
Rank 1
Rank 1
answered on 19 Mar 2013, 11:43 AM
Thanks Petur
A very clear and concise answer - just what I needed, thanks.
A very clear and concise answer - just what I needed, thanks.
0
Leo Tohill
Top achievements
Rank 1
Rank 1
answered on 16 Dec 2013, 02:48 AM
I had the same question, and found this answer, which explained it nicely. Thanks.
Is it just me, or is the terminology a bit weak? Why should the word "Server" imply a full page refresh? Both "Server" and "Ajax" binding call the server. In fact, they both do GET or POST (though I suppose with Ajax we can also see PUT and DELETE).
Just trying to get things clear.
Is it just me, or is the terminology a bit weak? Why should the word "Server" imply a full page refresh? Both "Server" and "Ajax" binding call the server. In fact, they both do GET or POST (though I suppose with Ajax we can also see PUT and DELETE).
Just trying to get things clear.