> The protocol is not raw TCP because it needs to provide the browser's "same-origin" security model. It's also not HTTP because web socket traffic differers from HTTP's request-response model.
If Websocket has something like crossdomain.xml does that mean we can build p2p applications on that?
If Websocket has something like crossdomain.xml does that mean we can build p2p applications on that?