Outline ·
[ Standard ] ·
Linear+
Linkedin chat does not use websocket
|
TS15cm
|
Feb 23 2024, 06:24 PM, updated 2y ago
|
|
i was surprised when i probed their website i am not going to post the full url because i am worried might expose some of my personal details but the url that handles chat messages is a GET request, something that looks like this https://www.linkedin.com/voyager/api/voyage...ssengerMessages. how does that work? I thought anything requires real time connectivity must use websocket?
|
|
|
|
|
|
soul78
|
Feb 23 2024, 07:20 PM
|
|
why need persistent connection for text?... you every second send text non stop?.. client server architecture with sockets can be yse but only for realtime data and exclusive use cases... for all others.. getting the text msgs 1sec or 10secs later does not matter...
|
|
|
|
|
|
silverhawk
|
Mar 7 2024, 01:33 AM
|
Eyes on Target
|
QUOTE(15cm @ Feb 23 2024, 06:24 PM) i was surprised when i probed their website i am not going to post the full url because i am worried might expose some of my personal details but the url that handles chat messages is a GET request, something that looks like this https://www.linkedin.com/voyager/api/voyage...ssengerMessages. how does that work? I thought anything requires real time connectivity must use websocket? They did share some details here: https://www.linkedin.com/blog/engineering/a...s-of-thousands-Websockets aren't the only way to do real time chat. If you actually think about it on a large scale, keeping that many persistent connections open is a huge resource constraint on your servers and network. Even chat apps like whatsapp don't really use websockets
|
|
|
|
|