Is my websocket session idea practical?
In a situation where all communication (including logging in) between a client (web browser) and server is done over a persistent TLS encrypted websocket, would there be anything inadvisable about having the server attach the client’s log-in state to the connection itself as custom properties?
Is my websocket session idea practical?
In a situation where all communication (including logging in) between a client (web browser) and server is done over a persistent TLS encrypted websocket, would there be anything inadvisable about having the server attach the client’s log-in state to the connection itself as custom properties?
Is my websocket session idea practical?
In a situation where all communication (including logging in) between a client (web browser) and server is done over a persistent TLS encrypted websocket, would there be anything inadvisable about having the server attach the client’s log-in state to the connection itself as custom properties?
Strategy for creating a websocket relay? [closed]
Closed 8 years ago.
Strategy for creating a websocket relay? [closed]
Closed 8 years ago.
Is performance the only reason not to use SignalR (websockets) entirely in lieu of a traditional REST API?
I have used SignalR to achieve real-time messaging functionality in several of my projects. It seems to work reliably and is very easy to learn to use.
Should the async update-server be on the same physical server as the website?
I want to setup a comet/web-socket server for a forum sitting in front of a message queue i.e. rabbitmq, that will maintain client connections and update them about relevant events (i.e. new posts, topics, etc.)
Should the async update-server be on the same physical server as the website?
I want to setup a comet/web-socket server for a forum sitting in front of a message queue i.e. rabbitmq, that will maintain client connections and update them about relevant events (i.e. new posts, topics, etc.)
Two way Communication between Server and Clients
Situation: We have a web application running on a server. This application needs to fetch data from some other PC(Clients), which are on a different network.
Are there any design pattern to data binding in event driven architecture?
I develop a browser based game with node.js in back and HTML5 canvas in front-end.
It use WebSockets for communication.