Add parameter to set custom headers on the client
Do not allow overriding Sec- and other pre-defined headers
Merge pull request #58 from igorw/client-custom-headers

Add parameter to set custom headers on the client
Patch native compilation warnings.
Native XOR.

Improves xor efficiency with a native implementation replacing
WebSocketFrame::applyMask.

Includes configuration for wscript and bindings.gyp.

General cleanup by Rusty Burchfield <GICodeWarrior@gmail.com>.
Merge pull request #60 from GICodeWarrior/native-warnings

Patch native compilation warnings.
Merge pull request #61 from GICodeWarrior/xor

Native XOR.
Update README to include Safari 6
Add cstring include to native XOR.

The previous includes are sufficient for Ubuntu and Mac, but for whatever
reason, cstring is necessary for memcpy on CentOS.
Merge pull request #62 from GICodeWarrior/xor

Add cstring include to native XOR.
Making compiled modules optional
Eliminating wscript
Using explicit 'install.js' script to call node-gyp for building the native modules
Updating command-line usage for echo-server.js
Releasing version 1.0.7, overhauled native module build process and made native modules optional.
Updating npmignore to allow the README.md file.
Tentative resolution for Issue #55 - parse Cookies Bug
Adding clarifying information for build failure error message to let users know that the module will still work.
Fixing cookie parsing to be compliant with RFC 2109.  Closes Issue #55
Removing accidentally left over old parseCookies function.
Bug fix - parameter sanity check on parseCookies

During a websocket handshake, if the client does not pass a Cookie
header, then WebSocketRequest.prototype.readHandshake will pass an
undefined value to WebSocketRequest.prototype.parseCookies.

If the str parameter is undefined, then an exception will be thrown when
the .split() method is called upon it.
Note node-gyp requirement