Default IPC proxy timeout is too small in facade.py

[andrewbonney]

This is likely to be a compound issue. When using facade.py to register many thousands of resources with the Node API, the process slows down. When this happens the default IPC Proxy timeout of 100ms is regularly breached. Upon timeout a new connection is made and the old one never appears to be closed (causing a file descriptor leak). There are likely to be a number of small changes required to account for this:

• Increasing the default Proxy timeout (to a second for example) to work around the slowdown in the Node API
• Ideally improve performance within the Node API, as it becomes unworkably slow beyond around 2000 resources, and breaches the timeout of 1 second at around 4000 resources
• Ensure that when timeouts do occur, the Proxy connections are properly closed, and the caller handles the error condition correctly (it will likely be out of sync with the Node API as a result)

At present the interface is limited to around 1200 resources before it starts to cause errors on my test host.

[andrewbonney]

Traced the Node API issue which was down to the registration process listing all resources of that type every time a new one was registered... oops!