Testing the armoryd branch...and armoryd...

Setting up a watch-only wallet and make a php jsonrpc call works!
Now testing the process of getting unsigned transactions.
I have some troubles to add a additional watch-only wallet to armoryd.
I get this error after the notification 'Another instance of armoryd.py is already runnning!':
~/BitcoinArmory$ {
"error": {
"errortype": "exceptions.ValueError",
"extrainfo": "No JSON object could be decoded",
"jsoncommand": "armory_abc_.watchonly.wallet",
"jsoncommandargs": []
}
}
It looks like I have to put in some extra arguments to make a second armoryd work with another watch-only.
I can't find what the arguments should be. (has it something to do with: AuthServiceProxy def __call__(self, *args) ??)
Also I suspect armoryd does not except more arguments (your code states: # The only argument that armoryd.py takes is the wallet to serve)
Please let me know where to find some clues to get a second watch-only armoryd running.
I'm also wondering how the jsonrpc call is made. Is it to a different RPC_PORT? If not, how do I make a jsonrpc call to a specific wallet? If so, how do I know the rpc_port's of all wallets running?
I'm also wondering if it is possible to make use of the authentication of the (proxy) service to identify a wallet/user from the (php) jsonrpc. (otherwise I have to make a authentication for a wallet/user before the (php) jsonrpc call's could be done)