title: Architecture recommendation for cancellable backend calls [zerorpc if possible?]
body: <p>I have an electron app frontend (zerorpc-node) communicating with a python backend (zerorpc-python) that needs to:</p>
  
  <p>a) be able to send requests to the backend [standard zerorpc call]</p>
  
  <p>b) be able to run multiple backend processes simultaneously [followed the architecture in <a href="https://github.com/0rpc/zerorpc-node/issues/96" rel="nofollow noreferrer">https://github.com/0rpc/zerorpc-node/issues/96</a>)</p>
  
  <p><strong>c) be able to cancel a backend process at will [not sure how to do this with current architecture]</strong></p>
  
  <p>Any guidance on how to architecture a solution to (c) would be great. If necessary I am willing to switch away from zerorpc if it is limiting, but if the solution involves using zerorpc that's fantastic.</p>