Understanding client_id in the message bus

Alexander · April 19, 2024, 12:01pm

I could be wrong, but the clientId is likely to identify who the MessageBus should deliver X message to

Imagine it as a conversation where every X amount of time, the client asks the server “Hey, I have id XYZ, do you have a message for me?”

The client id seems to be automatically generated every time the script is loaded (I don’t know if in the case of Discourse this generated clientId somehow persists on the client)

github.com/discourse/message_bus

assets/message-bus.js

c1ed81dee


      
              var r = (Math.random() * 16) | 0;
              var v = c === "x" ? r : (r & 0x3) | 0x8;
              return v.toString(16);
            });
          };
          
          var me;
          var delayPollTimeout;
          var ajaxInProgress = false;
          var started = false;
          var clientId = uniqueId();
          var callbacks = [];
          var failCount = 0;
          var baseUrl = "/";
          var paused = false;
          var later = [];
          var chunkedBackoff = 0;
          var stopped;
          var pollTimeout = null;
          var totalAjaxFailures = 0;
          var totalAjaxCalls = 0;

Topic		Replies	Views
How discourse stays online (Message Bus, Faye, Long Polling) Development	25	19057	January 4, 2022
Message-bus is duplicating headers in Discourse chat Development chat , rest-api	6	674	February 13, 2024
Long Polling Message Bus Notifications from React Application Development	4	1440	February 27, 2020
Dealing with the limited messagebus backlog Development	9	1511	April 23, 2017
How does Discourse update the client on new posts from the server? Development	2	1119	February 15, 2019

Understanding client_id in the message bus

Related topics