Get list of open connections from JS SignalR client? - javascript

I have a site I'm developing, and I open quite a few connections to my SignalR hub. Sometimes, a call to HubConnection.start hangs, and I suspect it's because the client's at some kind of open connection limit. Is there a way I can get a list of all open SignalR connections from the JS client side?

Related

How to handle client losing Internet connection with socket.io

I am fairly new to Web development so bear with me.
Setup:
I am running a server on my localhost and I am also running a web application (via webpack) which represents a client. Ideally a client would be someone visiting my webapp via a mobile phone for example.
Now the client creates a socket (using socket.io) and connects to the server. Then server starts sending data to the client. The client uses the data to alter the state of the webpage. The client also has some local data (accessible from the client side once the web page has loaded) to change state if it receives no data from the server.
Problem:
I want to be able to detect when the client loses internet connection (and therefore connection to my server), so that the webpage can then start using the locally available data to change state. I thought about using Detect the Internet connection is offline?
to do this, but I am unsure if this is even the right approach. Is there a way to achieve this using socket.io? I am aware of socket.on('disconnect', ...) but I am unsure if this would fire if the client himself loses connection.
you can use the socket.on('disconnect', ...) on client side script

Find and Close All Websockets from Client

My Angular application dependency is opening websockets via sockjs (but they are just normal websockets, obviously). I do not have access to the websocket objects, so I can't just call close on them.
These open connections are interfering with some other logic.
How do I programatically find ANY and ALL websocket connections and close them?

Disconnected clients remaining online on Openfire server with websockets

I'm using Openfire as XMPP server and I added the websocket plugin to it in order to improve some chat features (i.e. file transfer).
Communication via xmpp among my web clients works fine but there is an issue on client network disconnections or changes.
In fact in those cases disconnected clients still remain online in the server, even if a timeout in the idle connection policy is set.
No ping is sent to the clients, so openfire never checks if client connections are active or not.
I've seen that an issue is still open: https://igniterealtime.org/issues/browse/OF-963
Is there a workaround to avoid disconnected clients remaining online on Openfire server with websockets?
I use older version, exactly 4.0.2 I think for my Openfire installation as this BUG is not fixed yet.
This is the reason why messages are sent from another client and lost, cause first client appear as online and in reality it is not regardless the time interval you set in Openfire config after which it will disconnect clients.

Locate server on LAN in JavaScript

TL;DR
In Javascript, how do you to find the IP of all servers running a specified program on a specified port in the LAN?
Background
I'm writing a server in node.js that is supposed to connect users browsers as controllers to a common device on which a game is running. The browsers are running a web app based on html and Javascript. The connection is based on socket.io.
I'd like for the web app to be able to find all available instances of this server in the LAN in order to create a server list for the user to choose from.
Is there a way to make the server discoverable by the web app on the local network in Javascript, and in that case: how?
Ideas
Have the server broadcast its IP to all devices on the LAN and have the web app listen for these messages (No idea how to do this without node on the client)
Connect to every IP on the network and see if the connection is successful. (Does not seem feasible)
Scan every IP on the network and connect only to those where the port is open. (Once again, no idea how to do this without node on the client and does not seeem feasible either.)
EDIT
The server is supposed to be portable and work independently, without any central system backing it up or providing matchmaking for clients. It is a LAN only server and should work even without internet access.
There is no way for you do this. Sorry. Since there is no exposure to UDP on client-side JavaScript, broadcasting is out of question. Any attempt on massive scanning will quickly raise flags on network monitoring software. You have to use a known address.

For a push notification, is a websocket mandatory?

I have PHP on the server side, and HTML and javascript on the client side.
I am making an app where a stakeholder types a message that is broadcasted to multiple recievers of a group in real time.
I did some research on google and I understand I need to use WebSockets or Comet for real time push notifications. Is WebSocket or Comet mandatory for sending mass notifications to users?
Is my understanding correct? Any references to start with?
If the client is a browser, then the ONLY two ways a standard browser can connect to a server is via an Ajax (e.g. http) request or a webSocket connection. So, if you want a client to get notified of something from the outside world it has to use one of those two mechanisms.
HTTP requests are transitory. The client makes a request of a server, the server responds. HTTP requests are perfect for the client requesting information from the server. They are not very good at the server sending information to the client because normally the client is not connected. There are hacks and work-arounds where the client "polls" the server on some interval and maybe even the server uses longer running requests to try to simulate a "push" type system, but they are sub-optimal hacks at best.
webSockets are continuous connections. The client connects and the connection remains in place for as long as both sides want. This allows either side the ability to send a message to the other side whenever they want. That means the server can "push" data to the client whenever it wants. webSockets are efficient for push connections and are recommended (this is one of the main things they were designed for).
Comet is a library that was originally built for using HTTP to try to "hack" or "simulate" push before webSockets were invented and then before they were widely supported. I can think of no reason why one would want to use Comet instead of a webSocket unless you had such an old browser that webSocket was not supported.
So, if you are trying to do "realtime server push" to a browser, then you must have a continuously connected socket from the client which means webSocket (or something built on top of webSocket like socket.io).
For phone apps where you have access to the phone SDK, you can use the "push" system built into the OS to push some messages from server to client. This isn't quite the same as the two way webSocket channel, but since you asked about "push notifications", the OS push services available in both Android and IOS could also be an option for pushing notifications from server to client. Here's info on iOS notifications and Google Cloud Messaging
As of 2016, one can also use Server-sent events in all modern browsers except Microsoft browsers (not supported yet in Edge or IE) to push data from server to client. Here's a browser compatibility table. Server-sent events use a long lasting HTTP connection, a special MIME type and a supporting client in order to be able to send events from server to client at any time. Unlike webSockets, server-sent events are one way only (from server to client). A client would then use a traditional Ajax call in order to be able to send data to a server (whereas with a webSocket data can be sent either way over the same webSocket connection).
Here's a good description of how server-sent events work: How do server-sent events actually work?
Is your client application a SPA? (Single Page application)?
It's very important because if not, you have to consider that everytime a client change page, connection with websocket server will be lost.
In this case you have to manage a queue because if stakeholder send a multicast request when one client is disconnected, client won't receive nothing.
Polling won't solve this situation too and it's an orrible solution because mobile clients (for example) with typical internet plan, will consume megabytes for unuseful "ping" traffic.
A real example of polling is a child in a car asking his dad every minute if they are arrived to a destination!
So, Is there a solution without using spa?
Yes, using a "shared storage" between stakeholder and clients, and using websocket only for "wake up" online clients saying: Hey there is something new, go to check!
Everytime a client open a page it will receive from backend also not-read notifications, taken from the storage.
When a stakeholder want to notify something, it will just store the notification message in the shared storage and send a "pulse" to notification server.
Notification server will forward the "pulse" to online clients (just in case someone is stuck reading a page).
If a "pulse" is lost because a client is changing page there is no problem because the client will bring notifications from the storage.
Every page will contain this logic:
Retrive number or unread notifications (server side)
Connect to the notification server after 5 seconds (javascript side).
Hope it helps.
I would suggest that using webSockets is a more efficient way compared to other options, why is this? Well when a client receives a notification that there's a change in the server there is no need to create an AJAX call to the server to get that change, it can be sent to the client with the same webSocket connection more easily than AJAX. This means efficient code and a faster running App!

Categories

Resources