thanks for adding my contribution.
I would like to propose you a tiny convenience improvement for BC JS Remote.
I am setting up BC JS Remote to access several instances of bitcoind running in the same box; more specifically a testnet-in-a-box configuration:http://sourceforge.net/projects/bitcoin/files/Bitcoin/testnet-in-a-box/
Using a fixed value for RPC.url in the settings.json file is a difficulty for multiple access, because there is no way to instruct Apache to proxy to/from every bitcoind instance.
My proposal is following behaviour; if the RPC.url field is undefined, it is automatically assigned to a value derived from the directory part of the URI. For instance,
Accessing with http://mydomain/jbc1
leads to a RPC.url value of "/jbc1/bitcoind/, and
accessing with http://mydomain/jbc2
leads to a RPC.url value of "/jbc2/bitcoind/
This allows us to setup different Proxy directives for the Apache webserver. For instance:
ProxyPass /jbc1/bitcoind/ http://localhost:19331/
ProxyPass /jbc2/bitcoind/ http://localhost:19332/
Is an interesting improvement for you?, could you code such a suggestion?
Also, I could pull a patch for BC JS Remote, my experience coding JS is limited but acceptable.