am developing a single page for monitoring purpose , some of data in this page come through a websocket as a realtime monitoring , and other data fetched from the database as a historical report .
My Question :
Should i establish the websocket connection in the backend and then send the data to the connected client OR just connect to the websocket server in client side .
Note:
- no need to save the messages come from the webscoket server.
Please i need details .
Thanks
Related
I have an issue with connecting to my databases via desktop client. I use ssh key to connect to my server via console and I am able to connect to my live server.
But no luck for my database connection. I use TablePlus as my desktop client and I keep getting SSH Error, can't connect to host. That's all I get.
How can I find out what the problem is exactly?
I have a front-end angularJS server that is getting data from a back-end nodeJS server from MySQL DB via middleware.
I created a front-end simple login form that needs to send data for authentication to the back-end server (checks if user exists in the db).
The back-end server returns user details in the case that the user is found in the DB or prints error login message or redirect to signup screen.
I'm looking for a guide or example on how to create a correct authentication system with sessions and cookies between the two servers.
Thank you.
You should choose use a token authentication or use cookies.
Take a look at this,it is a good guide :
http://code.tutsplus.com/tutorials/token-based-authentication-with-angularjs-nodejs--cms-22543
I have a WPF application which communicates with a WCF service which provides data that is updated by WPF application on its UI on continues basis. The Service is hosted on netTCP. Now, if for some reason the WCF app loses its LAN connection and after a few seconds the connection is established again, the WPF app is not able to resume its connection with the service.
Any help is welcomed.
You could make a socket on the WPF client, which will accept a connection from the service, then if the service is back online again it sends a data packet to everyone in the collection currently connected, then if the client recieves a packet it requests a connection with the service again, which will "resume" the connection
We have a load balanced webserver setup and we therefore want to use SignalR for client/server communication with a SignalR backplane.
How can we make sure that only one server writes to the database when a client sends something to the server? The backplane will re-route the message to all servers, but not all servers can write the same thing to the DB!
Any techniques/suggestions for how I can both use the SignalR backplane and only write to DB from one server?
In my ideal world I would receive the message on one server, store message to DB and then put a message (maybe not the same as the incoming message) on to the backplane.
The SignalR backplane only forwards messages sent from the server to client to all servers. This is done so SignalR can ensure messages will get to their intended client(s) even if they are connected to another server.
When a SignalR client invokes a Hub method, the Hub method is only invoked on one server even if there are multiple SignalR servers behind a load balancer communicating via a backplane.
Is there a way to send message or http request or send notification when SQL Azure data changes or when new data is inserted? I would like to send message/ http request/ notification to a non .NET web application. I have done that invoke an application of Tomcat server by send a http request from local SQL server when there is data change, but I can't with SQL Azure.
Can any one help me to solve this problem?
I hope it is ok to talk about our own Cotega service. IF you are interested in a finished solution for this, we are just finishing off the work to allow people to send Email and SMS notifications messages based on changes within their SQL Azure database so it would be interesting to see if we could extend this to suit your needs to call a .NET web app. Feel free to contact me from here if you are interested.