Ideally, I think that should be handled at the api level. Say program A sends a request to service X on program B, and as a result program B needs to send a request to service Y on program A. My solution would have service X import a client for service Y (with no global state in the transport method), and then use the methods in service Y as needed.
- Re: Nerve: RPC framework for Nim nepeckman
- Re: Nerve: RPC framework for Nim rokups
- Re: Nerve: RPC framework for Nim nepeckman
- Re: Nerve: RPC framework for Nim rokups
- Re: Nerve: RPC framework for Nim nepeckman
- Re: Nerve: RPC framework for Nim rokups
- Re: Nerve: RPC framework for Nim nepeckman
- Re: Nerve: RPC framework for Nim rokups
- Re: Nerve: RPC framework for Nim nepeckman
- Re: Nerve: RPC framework for Nim rokups
- Re: Nerve: RPC framework for Nim nepeckman
- Re: Nerve: RPC framework for Nim nepeckman
- Re: Nerve: RPC framework for Nim rokups
- Re: Nerve: RPC framework for Nim nepeckman
- Re: Nerve: RPC framework for Nim nepeckman
- Re: Nerve: RPC framework for Nim kidandcat
- Re: Nerve: RPC framework for Nim rokups
