I’ve learn many articles and watched many tutorial movies, however the frequent floor for many of the materials is to Publish adjustments to ALL customers. Not Subscribing and get info what considerations simply the person who’s logged in.
The opposite frequent floor is Websockets protocol. There appears to be many different methods to pores and skin this cat (Mark Twain) and I’ve some doubt which one to selected.
What I’m trying to find is a means for the person to login and hook up with a server (Websocket server?) and say one thing like “Hey, I’m Joe, please maintain me up to date on MY stuff”.
I’ve managed to arrange a websocket server, however I solely will get extra confused how one can proceed. The way to suppose? The closest I’ve discovered is that this and discovered additionally this. However that is above my pay grade. I do perceive nothing.
On this stage I’m largely fascinated with “how one can suppose”? No language particular.
Any enter or route is welcome!
Did you look into utilizing present messaging techniques like NATS?
By no means heard of it. What’s the large distinction evaluating to Gorilla/Websocket?
Do I perceive this appropriate that you could mimic “rooms” in Socket.io this fashion? ClientID = “room”?
sc, err := stan.Join(clusterID, clientID, stan.NatsURL(url),
And the way do I get “Joes stuff”? Ship a question to Postgresql? As soon as or each 5 minutes?
We’re speaking about completely different ranges right here. Websockets is a community communication protocol on the identical protocol degree as HTTP, whereas NATS is a message-passing system that runs on high of community protocols like TCP or Websockets.
I’m not acquainted with Socket.io and can’t let you know something that’s not already of their docs. Evidently Socket.io does have some form of broadcast mechanism utilizing so-called rooms that permit sending messages to purchasers who joined that room. This sounds fairly like what you’re on the lookout for—an answer to publish messages to subscribed purchasers.
Sure! I’ve examine NATS and it appears value a attempt. And I can begin the NATS-server on a Debian 10, however it appears that evidently the server doesn’t pay attention.
[3265] 2022/10/04 11:28:20.779634 [INF] Beginning nats-server
[3265] 2022/10/04 11:28:20.779813 [INF] Model: 2.9.2
[3265] 2022/10/04 11:28:20.779846 [INF] Git: [6d81dde]
[3265] 2022/10/04 11:28:20.779883 [INF] Title: NDQU3V6PO7F63NIRX7AC65QZKB3DM73OIJADYBIO2JJMQOEE5HZSYE4Q
[3265] 2022/10/04 11:28:20.779911 [INF] ID: NDQU3V6PO7F63NIRX7AC65QZKB3DM73OIJADYBIO2JJMQOEE5HZSYE4Q
[3265] 2022/10/04 11:28:20.780183 [FTL] Error listening on port: 127.0.0.1:2222, "pay attention tcp 127.0.0.1:2222: bind: handle already in use"
I discovered the executable nats-server-v2.9.2-linux-amd64 right here I exploit this command to begin the server:
cd /residence/nats/
./server --a 127.0.0.1 --port 2222
No Docker concerned. Mainly I adopted roughly this instruction.
Any clue what I’m doing fallacious?
