what if we don't want the clients with old browsers ? Why doesn't SignalR release a WebSockets only client library that should be something around 3-4 kb and let us choose. Or even better without any client library for connecting to the WS endpoint and the library should be needed only for sending and receiving data not for connecting. With pure simple WS we can pre-connect without any other code loaded in the client and then speed up the loading time of websites time so much by sending/receiving data this very first moment that JS loads.
When I first did a remote control type app, my coworkers were wondering how the web was changing. I just started coding a System Monitor app that I will program with a micro-script over signalR. SignalR is a very useful tool. I need to add some security though, cause so far I'm using it like a message pump and hacked my own service to do things it wasn't designed to do.
I would say that: SignalR gives a nice event-driven interface for real-time communication that sit on top of various protocols. Socket.IO in JavaScript essentially does the same thing.
what if we don't want the clients with old browsers ? Why doesn't SignalR release a WebSockets only client library that should be something around 3-4 kb and let us choose. Or even better without any client library for connecting to the WS endpoint and the library should be needed only for sending and receiving data not for connecting. With pure simple WS we can pre-connect without any other code loaded in the client and then speed up the loading time of websites time so much by sending/receiving data this very first moment that JS loads.
When I first did a remote control type app, my coworkers were wondering how the web was changing. I just started coding a System Monitor app that I will program with a micro-script over signalR. SignalR is a very useful tool. I need to add some security though, cause so far I'm using it like a message pump and hacked my own service to do things it wasn't designed to do.
I would say that: SignalR gives a nice event-driven interface for real-time communication that sit on top of various protocols. Socket.IO in JavaScript essentially does the same thing.
I dislike that everything has to be DI now, even SignalR.
why?