Mist doesn't support websockets

[jorisbontje]

$ mist -h
invalid boolean value "on" for -ws: strconv.ParseBool: parsing "on": invalid syntax
mist [options] [filename]:
options precedence: default < config file < environment variables < command line
  -asset_path="/usr/local/Cellar/go-ethereum/0.7.10-49/Resources": absolute path to GUI assets directory
  -conf="/Users/mids/.mist/conf.ini": config file
  -datadir="/Users/mids/.mist": specifies the datadir to use
  -debug="": debug file (no debugging if not set)
  -export="": exports the session keyring to files in the directory given
  -genaddr=false: create a new priv/pub key
  -id="": Custom client identifier
  -import="": imports the file given (hex or mnemonic formats)
  -keyring="": identifier for keyring to use
  -keystore="db": system to store keyrings: db|file (db)
  -logfile="": log file (defaults to standard output)
  -loglevel=3: loglevel: 0-5: silent,error,warn,info,debug,debug detail)
  -maxpeer=30: maximum desired peers
  -port="30303": listening port
  -rpc=false: start rpc server
  -rpcport=8080: port to start json-rpc server on
  -seed=true: seed peers
  -upnp=true: enable UPnP support
  -vm=0: Virtual Machine type: 0-1: standard, debug
  -ws=false: start websocket server
  -y=false: non-interactive mode (say yes to confirmations)

Even tough the mist command line help suggests that the websocket server can be enabled, providing -ws=true doesn't actually start a server.

I would suggest to either remove it from the help output, or add WS support to the mist client.