I suggest you ...

Add support for Web Sockets

Add support for Web Sockets to enable push notifications to grid, listview, and other data bound widgets.

246 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    briankbbriankb shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    6 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • HansHans commented  ·   ·  Flag as inappropriate

        > Can you elaborate further what do you mean by web sockets support for push notifications for some of the widgets? What restricts/limits you from using web sockets for this purpose now, under browsers which support them?

        The current implementation is AJAX oriented, as the Transport object of the DataSource is not aware of WebSockets.

        The net effect of using Websockets would be the appearance if instant changes propagation from both sides, as can be seen e.g. in Meteor ( http://www.meteor.com/ )

      • qwertyqwerty commented  ·   ·  Flag as inappropriate

        We are beta testing using websockets with Kendo Mobile and Web and haven't had any issues binding the data to the UI elements. All we did was just bind the data transported to the kendo datasource.

        var jsdata = JSON.parse(websocketdata);

        $("#top25-listview").kendoMobileListView({
        dataSource: jsdata,
        template: $("#top25ListViewTemplate").html()
        });

      • James HancockJames Hancock commented  ·   ·  Flag as inappropriate

        HTML 5 websockets so that instead of the previous polling suggestion, we open a socket to the server, and the server responds when there is new information and then we do a get, or the response in the websocket is the new data set.

      • John Douglas FarrarJohn Douglas Farrar commented  ·   ·  Flag as inappropriate

        I believe the desire is to create open channels where the content updates can be initiated from the server. Currently page updates are initiated from the browser/client in a request response pair. Then the result is used to interact with the page. In a web socket we would have a channel connection and it would seem a router event handler for incoming socket communications.

      Feedback and Knowledge Base