The abomination that is SignalR. That's it. That's the rant.

You'd rather roll websockets by hand?

I've used it before and didnt find it that bad.

i used it in .net, and i used it in JS, and it seemed fine.

what seems to be the problem?

@Midnight-shcode seems flaky at times. This is .net core signalr hosted on azure.

@fullstackchris I'm only responsible for consuming it :)

@cygnus the one i was using was noncore hosted on a real server. maybe azure is the problem =D

@cygnus your problem isn't SignalR. that's actually a fine invention. your problem is azure, which is so terrible, it was even banned in hell.

The problem with SignalR is its awful connection management. It really gets disconnected way too often.

Sure, It has automatic reconnections but that's to a certain extent. After that, the disconnection is "final" and you need to manage It yourself. Not ideal.