The final option to consider is to just let users send and receive UDP packets directly from the browser. Of course, this is an absolutely terrible idea and there are good reasons why it should never be allowed. (1) Websites would be able to launch DDoS attacks by coordinating UDP packet floods from browsers. (2) New security holes would be created as JavaScript running in web pages could craft malicious UDP packets to probe the internals of corporate networks and report back over HTTPS. (3) UDP packets are not encrypted, so any data sent over these packets could be sniffed and read by an attacker, or even modified in transmit. (4) It would be a massive step back for web security to create a new way for browsers to send unencrypted packets. (5) There is no authentication, so a dedicated server reading packets sent from a browser would have to implement its own method to ensure that only valid clients are allowed to connect to it, which is well outside the amount of effort most game developers would be willing to apply to this problem.