Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 2 years ago.
Improve this question
I'm creating a real-time, multiplayer browser game using the ws websocket library in Javascript. I've seen multiple posts talking about the reconnection for their websockets. However, I don't understand why reconnecting the websocket is necessary. Are websocket connections inherently unstable and thus close regularly (~5mins)?
So my questions are, what are the main reasons people implement reconnection into their websockets? And what are the causes of the disconnections?
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 12 months ago.
Improve this question
I am writing an android app using Java and for the back-end I chose socket.io in node js.
I just want to ask what happens if I socket.io instead of rest-api?
Using socket.io as the main communication system is not a good choice because the communication system is always open.
now imagine 1000 people want a data trough sockets, it will slowdown your server and sometimes cause server crashes.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
I'm trying to write a web application which needs to exchange messages with a local Smart Card.
Currently I'm trying to use WebUSB API to connect the Chrome with the smart card reader, but I'm struggling to use the PC/SC specification.
In my researches I found this two topics:
Architectures to access Smart Card from a generic browser? Or: How to bridge the gap from browser to PC/SC stack?
How to send APDU to PCSC reader from web broswer using javascript
Although they deal with the same subject, they have no connection examples.
If anyone has any tips or example of connection I would be grateful.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I want to know when should I choose this solution.
Is it just for solving cross domain communications on client browser?
Channel Messaging offer two-way and direct communication between browsing contexts. The DOM is not directly exposed with cross-document messaging but at each end there is a port. The data being sent from one port is the input in other and vice-versa. This will be a good article for you. And another article
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
Is it possible to implement webRTC at server side? ie., I want my browser to connect to a http server(tomcat which runs a java based app to stream a video) using webRTC protocol and get the streem from the server?
I think compiling webRTC api and access it through JNI will help. Any other easy directions to do this?
There is now a server-side implementation of WebRTC in Asterisk that should enable that: https://wiki.asterisk.org/wiki/display/AST/Asterisk+WebRTC+Support
I haven't yet looked into it that much so I can't say for sure that it does what you want.
Take a look at Lynckia's Licode Project. It is however, Node.js serverside.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 2 years ago.
Improve this question
I want to develop a web-based collaborative editing app: basically many users will transcribe a big mp3. The first step is to write a specification.
It seems pretty easy to do it with async communication and javascript, keeping track of the transcription an user gives and forwarding it to other users editing the same file, but I fear I might be underestimating the problem: what are the common issues this kind of problem raises?
Thanks!
You didn't specify what browsers you want to support. To do it "real-time", you can either poll the server or use Comet or WebSocket (for browsers that support it) or Flash net Socket. As with any collaborative app, I think the hardest problem is conflict resolution/keeping all sessions synchronized.
You might be interested in reading Google Wave Protocol too. It's a white paper on real-time collaborative document editing. Not for the faint of heart :D