The `routeRpc` macro does not actually send the result to the client, it just does the procedure dispatch and comes back with the response. It falls on the user to implement the network code, HTTP server, websocket server, or whatever else, then they can use `routeRpc` inside that network code. Should be no global state 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 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
