>It is transport agnostic in that the concepts can be used within the same process, over sockets, over http, websockets, or in many various message passing envi

>It is transport agnostic in that the concepts can be used within the same process, over sockets, over http, websockets, or in many various message passing environments. I think tRPC sort of implements a transport layer for (a superset of) this, no?