Preface In this answer, I’ll assume the following: You’re not interested in using <p:push> (I’ll leave the exact reason in the middle, you’re at least interested in using the new Java EE 7 / JSR356 WebSocket API). You want an application scoped push (i.e. all users gets the same push message at once; thus you’re … Read more
I was in the same boat as you recently, and here is what I did: I used the phpwebsockets code as a reference for how to structure the server-side code. (You seem to already be doing this, and as you noted, the code doesn’t actually work for a variety of reasons.) I used PHP.net to … Read more
Client side Hixie-75: Chrome 4.0 + 5.0 Safari 5.0.0 HyBi-00/Hixie-76: Chrome 6.0 – 13.0 Safari 5.0.2 + 5.1 iOS 4.2 + iOS 5 Firefox 4.0 – support for WebSockets disabled. To enable it see here. Opera 11 – with support disabled. To enable it see here. HyBi-07+: Chrome 14.0 Firefox 6.0 – prefixed: MozWebSocket IE … Read more
Updated 2x Short answer: No, only the path and protocol field can be specified. Longer answer: There is no method in the JavaScript WebSockets API for specifying additional headers for the client/browser to send. The HTTP path (“GET /xyz”) and protocol header (“Sec-WebSocket-Protocol”) can be specified in the WebSocket constructor. The Sec-WebSocket-Protocol header (which is … Read more
Note: This is some explanation and pseudocode as to how to implement a very trivial server that can handle incoming and outcoming WebSocket messages as per the definitive framing format. It does not include the handshaking process. Furthermore, this answer has been made for educational purposes; it is not a full-featured implementation. Specification (RFC 6455) … Read more
WebSockets is definitely the future now. Long polling is a dirty workaround to prevent creating connections for each request like AJAX does – but long polling was created when WebSockets didn’t exist. Now due to WebSockets, long polling is going away no more. WebRTC allows for peer-to-peer communication. I recommend learning WebSockets. Comparison: of different … Read more
Websockets and SSE (Server Sent Events) are both capable of pushing data to browsers, however they are not competing technologies. Websockets connections can both send data to the browser and receive data from the browser. A good example of an application that could use websockets is a chat application. SSE connections can only push data … Read more
In the examples below the client is the browser and the server is the webserver hosting the website. Before you can understand these technologies, you have to understand classic HTTP web traffic first. Regular HTTP: A client requests a webpage from a server. The server calculates the response The server sends the response to the … Read more
Your class structure is wrong. The json string contains a list of face_list not a single object. Furthermore your current face_list class does not contain any properties just two nested class definitions which will not hold any values. Correct structure: public class FaceDetect { public int age { get; set; } public int beauty { … Read more