Fix sending next queued websocket notification.
Remove 'getaddressbalance' extension RPC.

Addresses do no have balances.  In situations where a payment is
required and just a single address was provided, it is better to track
the unspent outputs themselves, rather than watching some artificial
measure of payment.
Send btcdconnected ntfns to connected clients.

If a websocket client was already connected and the wallet and/or
chain server is loaded into the rpc server (enabling the handlers
specific to those components), the btcdconnected notifications were
not being sent, and this could break clients that expected the
notification.  I'm not happy with this change, but since this is how
notifications are currently done (unsolicited), and to not break
compatibility yet, I'm adding these back in for now.

Eventually, this notification will require explicit registration
before it is received by a client.  See issue #84.

Closes #115.
Fix typos from my last commit.
Fix build.
Use btcd-specific RPC user/pass for chain RPC.
Drain notification registeration channel.

This prevents a hang when attempting to set the wallet (and register
for wallet notifications) when the process is interrupted and the rpc
server begins shutting down.
Send btcdconnected notifications without a wallet.

The notified chain server connection state was being passed through
the wallet and then notified to the RPC server, which prevented this
notification from ever firing if a wallet didn't exist yet.  Instead,
make the RPC server register for these notifications directly from the
chain server RPC client.

I'm not happy with this notification and how it's handled in the code,
but to not break existing clients this change is being made.  Fixing
the notifiation mess and modifying existing clients to use a new
notification API will need to be done sometime later.
Save logs to network specific directories.

Fixes #114.
Register for ntfns when the RPCS creates wallets.

Previously, registerations for wallet notifications (new txs, changed
account balances) were only passed up to websocket clients if the
wallet was loaded off disk (SetWallet was called with a non-nil
wallet), and not for the case when the RPC server would create the
wallet (if it wasn't created yet, and the user manually created it
with createencryptedwallet).  This change fixes that by registering
for these notifications when this code path is taken.
Remove a unused channel from chain.NewClient
Refactor Wallet.txToPairs into smaller functions

Also add a unit test for one of them.
Drain chain server connected notifications.

Fixes a possible hang on shutdown.
Enable ScriptStrictMultiSig when creating or signing txs.

ok @jrick
Begin with root key index when reading keystores.

Instead of using the zero value, explicitly set the last chain index
to -1, which represents the root key.  If no additional keys are read
from the io.Reader, this could result in panics when looking up keys
at index 0, when no additional keys have been created yet.

Fixes #119.
allow client to disconnect when handlers are done

added a waitgroup on websocketClient to keep track of handler
goroutines specific to the client
IMPORT PATH MODIFICATION CHANGESET
----------------------------------

Please use this changeset as the first one on top of the conformal codebase.
Note that if there are new imports, they need to be changed as part of this
changeset. In general, use "git rebase" on github.com/conformal's version
and apply this changeset first.
Task #396 on Task Board:

Create a stub websocket call getdepositscript.