Right now our application is designed to facilitate all communication via websockets after the initial load.
We are trying to figure out a solution to safely pass se
With regard to cookies, it might be worth considering, that (currently), the WebSockets protocol spec does not require a browser to provide all, or even any of the cookies that were set by the web server originally serving the JavaScript you use to open a WebSockets connection to that server.
See here for a description of how Firefox behaves (from a FF developer).