I did a google search on wikipedia on websockets

WebSocket is a technology providing for bi-directional, full-duplex communications channels, over a single Transmission Control Protocol (TCP) socket. It is designed to be implemented in web browsers and web servers but it can be used by any client or server application. The WebSocket API is being standardized by the W3C and the WebSocket protocol is being standardized by the IETF. Since ordinary TCP connections to ports other than 80 are frequently blocked by administrators outside of home environments it can be used as a way to overcome these restrictions and provide similar functionality with some additional protocol overhead while multiplexing several WebSocket services over a single TCP port. 

Can I use websockets and your library to do any of the following
     
   - Access a remote application
   - Control the mouse of the target pc
  - Write directly to a shared image or whiteboard
  - Stream music
  - Control/access a remote application
  - Send keyboard signals to another application

Processing is powerful and I want to find new ways to be able to use it.

a webosocket will allow you to talk to a processing sketch via javascript on a webpage in a TCP kind of way.   So you could write a webpage that could control (bi-directionally) how your sketch is running (a remote gui)  

Looks like the link 404'd. Do you still have this code up anywhere? Thanks!

You can try and go up to the top level, but the page is based on "mystery meat" (no text, not even a title tag) and discourages exploring.

Thanks Matt. Much appreciated!

FYI:
Flaws have been discovered in the protocol -
http://hacks.mozilla.org/2010/12/websockets-disabled-in-firefox-4/
and there is a newer version of the draft than the comment in your code -
http://datatracker.ietf.org/doc/draft-ietf-hybi-thewebsocketprotocol/history/

I haven't tested the code in about a month maybe... and I use chrome.  So are you saying it's broke :)

The security concerns are actually more general than websockets per se, but I'm sure they are scaring people like browser developers and hosting providers away from supporting it for now. It actually probably doesn't have much bearing on your specific code. I haven't really looked at your code yet, but, coincidentally, I was actually fooling around with this personally before you posted and before I found out about the security concerns and successfully connected someones Java websocket code with some PHP websocket server code via Processing.

I'm no expert, but looking at the discussion on that article I posted it appears that an attacker would have to control a webhost that allowed websockets. So if you code with good intentions and security it shouldn't be possible to hijack your application for this exploit. I don't know if a hosting provider would trust users to deploy stuff like that though.

I used this Java client:
https://github.com/TooTallNate/Java-WebSocket

and this PHP server:
https://code.google.com/p/phpwebsocket/issues/detail?id=16
(a simple implementation of the class posted there)

The link to AnalogPixels github code has now changed