Dreadnought Browser Status

Using the Fastevents and Net2 libraries added no noticable performance increase, so it appears those were dead ends. It did make me think of a new architecture, though. I am going to try using 2 channels, 1 from the app to the browser (basically the channel I already have), and also a new channel from the browser to the app. The second channel will send event info to the app, including keyboard, mouse, window resize etc. This will be maintained as a state by the library, so when the app needs the info it is a local call. Also, I am going to see if I can get rid of confirmation return messages. Again the purpose here is to increase speed.