Is Binary Opcode encoding and decoding implementation specific in websockets?
<p>Suppose I am creating a websocket client. And a specific websocket url returns frame as 'Binary Frame (Opcode 2)' .The questions are <br><br> 1. Why would the developer want to wrap the original message inside a binary opcode frame?<br>
2. Is retrieving the message implementation centric? In another way, does the the client has to know the same logic that was used to encode at the server? <br> 3. If the above is false then is there a global way to decode/parse the binary opcode to see the actual data that is being sent?</p>