Announcement

Collapse
No announcement yet.

Linux 5.8 Lands A General Notification Queue

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Linux 5.8 Lands A General Notification Queue

    Phoronix: Linux 5.8 Lands A General Notification Queue

    Merged this weekend ahead of Linux 5.8-rc1 is the long-standing work on introducing a general notification queue for the kernel. The general notification queue was pushed back last year from merging but now the initial code is in shape for Linux 5.8...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    Is this going to feed D-BUS?

    Comment


    • #3
      Is this going to be like websockets?

      Comment


      • #4
        Originally posted by HarlemSquirrel View Post
        Is this going to be like websockets?
        websockets are for bi-directional communication, this only appears to be in one direction. What had you thinking this? Wouldn't something like unix sockets be similar to websockets instead?

        Comment


        • #5
          Originally posted by polarathene View Post

          websockets are for bi-directional communication, this only appears to be in one direction. What had you thinking this? Wouldn't something like unix sockets be similar to websockets instead?
          I was thinking of the pub/sub model that can be set up with websockets that can replace the need to repeatedly query an endpoint for updates. But yeah, not really that similar I suppose.

          Comment


          • #6
            Originally posted by HarlemSquirrel View Post

            I was thinking of the pub/sub model that can be set up with websockets that can replace the need to repeatedly query an endpoint for updates. But yeah, not really that similar I suppose.
            pub/sub model has nothing to do with websockets, websockets are just a plain two way communication channel, they is not model defined in it.
            What you are talking about is MQTT and maybe MQTT over websockets.

            Comment


            • #7
              Originally posted by dragonn View Post

              pub/sub model has nothing to do with websockets, websockets are just a plain two way communication channel, they is not model defined in it.
              What you are talking about is MQTT and maybe MQTT over websockets.
              Action Cable OverviewIn this guide, you will learn how Action Cable works and how to use WebSockets to incorporate real-time features into your Rails application.After reading this guide, you will know: What Action Cable is and its integration backend and frontend How to set up Action Cable How to set up channels Deployment and Architecture setup for running Action Cable

              Comment


              • #8
                "you can send messages to a server and receive event-driven responses without having to poll the server for a reply"

                - https://developer.mozilla.org/en-US/...WebSockets_API

                That is what made the connection in my mind but I'm sure this is quite different.

                Comment


                • #9
                  This is just some ruby implementation...
                  Maybe most websockets implementation are pub/sub model, but that doesn't mean websockets are implementing that model.
                  Websockets can by used in any possible way, I use websockets for streaming h264 video over it and view it in browser (h264-live-player) or as modbus to browser bridge.

                  Comment

                  Working...
                  X