AJAX or web sockets for client-server communication?
I recently took a course on AngularJS, and quite frankly I loved the concepts of a website that fetches json to handle subsequent requests, however I still feel like Javascript is far too slow for what I want to do on a server.
AJAX or web sockets for client-server communication?
I recently took a course on AngularJS, and quite frankly I loved the concepts of a website that fetches json to handle subsequent requests, however I still feel like Javascript is far too slow for what I want to do on a server.
AJAX or web sockets for client-server communication?
I recently took a course on AngularJS, and quite frankly I loved the concepts of a website that fetches json to handle subsequent requests, however I still feel like Javascript is far too slow for what I want to do on a server.
Socket connection to external IP through server
I am working on an application using sockets. Essentially I want to stream data between two clients. Since I can’t connect the two clients together directly (they aren’t on the same network), I will need to connect the two through a server.
Socket connection to external IP through server
I am working on an application using sockets. Essentially I want to stream data between two clients. Since I can’t connect the two clients together directly (they aren’t on the same network), I will need to connect the two through a server.
JavaScript Compression and Caching of Assets
I’m working on an idea that i can’t seem to find a good answer though hours and hours of searching,
JavaScript Compression and Caching of Assets
I’m working on an idea that i can’t seem to find a good answer though hours and hours of searching,
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?