[Feature Request] Add ability to specify a separate work server node

[gigaion]

In some scenarios two nodes will exist, one dedicated to work generation and another for the ledger.

Example scenario:

• Home node with power GPU (work generation node)
• Small stable node in an expensive datacenter with no GPU (Ledger node)

This is useful if you have a faster RPC node that is more powerful, but lacks the ability to do work_generate.

To back this idea, Nano's white paper specifically mentions this as best practice:

https://docs.nano.org/integration-guides/work-generation/#choosing-a-machine
Using a separate machine to manage work generation is recommended where possible.

You may refer to this previous pull request (Which instead can be improved upon by allowing specifying EXPORT example_url or flags):
#11
This feature will also need to tie into the existing feature request for doRPC Basic Auth ( #10 )

Figured since you've acknowledged recently that Joohansson's NanoRPCProxy is used a lot by the community, that this previous idea may be reconsidered.

[codesoap]

Sorry for the late response. I thought a little more about your request, but I still don't feel like this is a common requirement. I'll keep this issue open, to see if anyone else has a desire for this feature in the future.

Aside from that: Is there any popular software in existence right now, which supports the work_generate RPC, but not other, more common ones like account_info?