This answer on StackOverflow inspired me to write a full post about handling user interactions in desktop applications fashion using web sockets and ASP.NET MVC.
The main idea is to send commands to user interface from server-side code and handling the result on server side. As you know, the main problem in web is in the following, web working on request-response system, that means, when user send request to server, it generates the resulting markup for view. After it server waits for another request and so on.
I recommend to read this post, if you are interested at web development. If it would not be helpful for you, it could help you to understand some principles of architecture with web sockets.
Continue reading “User interactive abstractions handling at asp.net MVC”
Although there is documentation and demos for implementing binding to remote data, it can not be applied to the three-layer architecture. For example, if your web application does not have any local database and for displaying it’s content it is connected to the separated application via WCF or WEP API, which returns required data and you want to implement virtualization (or paging) including the set of basic grid operations, such as filtering, aggregations and sorting.
The following article could be useful if for the data retrieving you need to create instance of IQueryable and then working with the result of this query, also you does not trust Kendo UI .ToDataSourceResult() method, or want to implement some additional work on results, or you have some unrecognizable problems with using it.
Continue reading “Kendo UI for ASP.NET MVC grid virtualization to remote data”