News for hackers. Stuff that matters.

A comment on Back to basics: Why we chose long-polling over websockets. Parent comment

Re:Back to basics: Why we chose long-polling over websockets by whoknowsidont on Sunday January 05, 2025 @09:06PM (#42606843)
>Given the author mentions C# is part of their stack I don't know why they didn't mention signalr or use that instead of rolling their own solution.

Not saying this is why but SignalR is notoriously buggy. I've never seen a real production instance that didn't have issues. I say that as someone who probably did one of the first real world, large scale roll outs of SignalR about a decade ago.

[ Parent | on HN ]
Re:Back to basics: Why we chose long-polling over websockets by rswskg on Monday January 06, 2025 @09:29AM (#42610810)
I believe it's changed alot since then? I was abit cynical of it from that initial experience but recent usage of it made it seem reliable and scalable.
[ Parent | on HN ]
Re:Back to basics: Why we chose long-polling over websockets by davidgl on Friday January 17, 2025 @11:02AM (#42739205)
We use it in a production system on the aspnetcore stack, and it's been bulletproof for a number of years.

We have lots of proxies in the way, and old tech on certain networks, and at this moment we are 97% websockets, 2% server side events, 1% long polling, and it's all transparent to me, brilliant.

[ Parent | on HN ]