If you look at the code library mentioned in my previous post, you will noticed that the functionality in question is implemented by sending the current view's start and end dates as additional data of the read request
. Than on the server, the events are filters based on this date range and return back to the client. Note that the server operations are enable in order to instruct the DataSource to issue new request when date range, views current data etc. are changed.
Also note that in the navigate event
the "future" start and end dates are not available, as the event is triggered before
the view is actually navigated or changed. Therefore, only the new selected data is available.
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI