该用户的聊天记录定位。
I believe it's in the protocol. Each ws message sent to a client is a unique copy. We can't all look at the same stream with tcp/ws. But we can with UDP/Multicast. Again, I might be wrong
I believe it's in the protocol. Each ws message sent to a client is a unique copy. We can't all look at the same stream with tcp/ws. But we can with UDP/Multicast. Again, I might be wrong
And I thought multicast only works because of collocation, might be wrong tho
And I thought multicast only works because of collocation, might be wrong tho
well yeah I agree. Because the problem is that you have to send unique copies at each of the clients, and that sucks. But I don't see what would work better on the open internet, UDP would be really unreliable
well yeah I agree. Because the problem is that you have to send unique copies at each of the clients, and that sucks. But I don't see what would work better on the open internet, UDP would be really unreliable
Like, some multicast shit ? Aren't we stuck with ws because of the open internet anyway ?
Like, some multicast shit ? Aren't we stuck with ws because of the open internet anyway ?
even during office hours ? Nice and friendly office hours ?
even during office hours ? Nice and friendly office hours ?
But like, tiered rate limit like as the taker tiers ? So on wallets where you only make you are fucked, or am I understanding this wrong ?
But like, tiered rate limit like as the taker tiers ? So on wallets where you only make you are fucked, or am I understanding this wrong ?
Same, I could shave 20 microseconds from my 1000 milliseconds latency, totally worth it 💪🏼
Same, I could shave 20 microseconds from my 1000 milliseconds latency, totally worth it 💪🏼
when 2 clients are connected to the same websocket server, 1 of the client will get the information before the other. It is based on your skill to try and be the first client. The reason is that the "open" internet makes tradeoffs all the time, and you can play around that as a software/systems problem
when 2 clients are connected to the same websocket server, 1 of the client will get the information before the other. It is based on your skill to try and be the first client. The reason is that the "open" internet makes tradeoffs all the time, and you can play around that as a software/systems problem
How you handle the network depends on your skill. There is a bunch of things you can do to play around that
How you handle the network depends on your skill. There is a bunch of things you can do to play around that
well, network latency is latency anyway, so his message is still relevant 🙂
well, network latency is latency anyway, so his message is still relevant 🙂
https://discord.com/channels/710897173927297116/775506448041115669/1511414625776828437
https://discord.com/channels/710897173927297116/775506448041115669/1511414625776828437
Polymarket