feat: typed rpc

.vscode/settings.json

@@ -8,7 +8,7 @@
     "markdown"
   ],
   "editor.codeActionsOnSave": {
-    "source.fixAll.eslint": true
+    "source.fixAll.eslint": "explicit"
   },
   "search.exclude": {
     "**/.git": true,
@@ -44,6 +44,7 @@
   "js/ts.implicitProjectConfig.strictNullChecks": false,
   "cSpell.words": [
     "insx",
-    "Unport"
+    "Unport",
+    "Unrpc"
   ]
 }

README.md

@@ -36,6 +36,7 @@ Each of these JSContexts exhibits distinct methods of communicating with the ext
   - [Channel](#channel-1)
     - [.pipe()](#pipe)
   - [ChannelMessage](#channelmessage)
+  - [Unrpc (Experimental)](#unrpc-experimental)
 - [🤝 Contributing](#-contributing)
 - [🤝 Credits](#-credits)
 - [LICENSE](#license)
@@ -299,6 +300,133 @@ The `ChannelMessage` type is used for the message in the `onMessage` method.
 import { ChannelMessage } from 'unport';
 ```
 
+### Unrpc (Experimental)
+
+Starting with the 0.6.0 release, we are experimentally introducing support for Typed [RPC (Remote Procedure Call)](https://en.wikipedia.org/wiki/Remote_procedure_call).
+
+When dealing with a single Port that requires RPC definition, we encounter a problem related to the programming paradigm. It's necessary to define `Request` and `Response` messages such as:
+
+```ts
+export type AppletIpcDefinition = {
+  a2b: {
+    callFoo: {
+      input: string;
+    };
+  };
+  b2a: {
+    callFooCallback: {
+      result: string;
+    };
+  };
+};
+```
+
+In the case where an RPC call needs to be encapsulated, the API might look like this:
+
+```ts
+function rpcCall(request: { input: string; }): Promise<{ result: string; }>;
+```
+
+Consequently, it becomes a requirement to include a `CallbackId` at the **application layer** for every RPC method:
+
+```diff
+ export type AppletIpcDefinition = {
+   a2b: {
+     callFoo: {
+       input: string;
++      callbackId: string;
+     };
+   };
+   b2a: {
+     callFooCallback: {
+       result: string;
++      callbackId: string;
+     };
+   };
+ };
+```
+
+`Unrpc` is provided to address this issue, enabling support for Typed RPC starting from the **protocol layer**:
+
+```ts
+import { Unrpc } from 'unport';
+
+// "parentPort" is a Port defined based on Unport in the previous example.
+const parent = new Unrpc(parentPort);
+
+// Implementing an RPC method.
+parent.implement('callFoo', request => ({
+  user: `parent (${request.id})`,
+}));
+
+// Emit a SYN event.
+parent.port.postMessage('syn', { pid: 'parent' });
+
+// Listen for the ACK message.
+parent.port.onMessage('ack', async payload => {
+  // Call an RPC method as defined by the "child" port.
+  const response = await parent.call('getChildInfo', {
+    name: 'parent',
+  });
+});
+```
+
+The implementation on the `child` side is as follows:
+
+```ts
+import { Unrpc } from 'unport';
+
+// "parentPort" is a Port also defined based on Unport.
+const child = new Unrpc(childPort);
+
+child.implement('getChildInfo', request => ({
+  clientKey: `[child] ${request.name}`,
+}));
+
+// Listen for the SYN message.
+child.port.onMessage('syn', async payload => {
+  const response = await child.call('getInfo', { id: '<child>' });
+  // Acknowledge the SYN event.
+  child.port.postMessage('ack', { pid: 'child' });
+});
+```
+
+The types are defined as such:
+
+```ts
+import { Unport } from 'unport';
+
+export type Definition = {
+  parent2child: {
+    syn: {
+      pid: string;
+    };
+    getInfo__callback: {
+      user: string;
+    };
+    getChildInfo: {
+      name: string;
+    }
+  };
+  child2parent: {
+    getInfo: {
+      id: string;
+    };
+    getChildInfo__callback: {
+      clientKey: string;
+    };
+    ack: {
+      pid: string;
+    };
+  };
+};
+
+export type ChildPort = Unport<Definition, 'child'>;
+export type ParentPort = Unport<Definition, 'parent'>;
+```
+
+In comparison to Unport, the only new concept to grasp is that the RPC response message key must end with `__callback`. Other than that, no additional changes are necessary! `Unrpc` also offers comprehensive type inference based on this convention; for instance, you won't be able to implement an RPC method that is meant to serve as a response.
+
 ## 🤝 Contributing
 
 Contributions, issues and feature requests are welcome!

examples/child-process-rpc/child.ts

@@ -0,0 +1,29 @@
+import { Unport, Unrpc, ChannelMessage } from '../../lib';
+import { ChildPort } from './port';
+
+// 1. Initialize a port
+const childPort: ChildPort = new Unport();
+
+// 2. Implement a Channel based on underlying IPC capabilities
+childPort.implementChannel({
+  send(message) {
+    process.send && process.send(message);
+  },
+  accept(pipe) {
+    process.on('message', (message: ChannelMessage) => {
+      pipe(message);
+    });
+  },
+});
+
+// 3. Initialize a rpc client
+const childRpcClient = new Unrpc(childPort);
+childRpcClient.implement('getChildInfo', request => ({
+  clientKey: `[child] ${request.name}`,
+}));
+childRpcClient.port.onMessage('syn', async payload => {
+  console.log('[child] [event] [syn] [result]', payload);
+  const response = await childRpcClient.call('getInfo', { id: '<child>' });
+  console.log('[child] [rpc] [getInfo] [response]', response);
+  childPort.postMessage('ack', { pid: 'child' });
+});

examples/child-process-rpc/parent.ts

@@ -0,0 +1,43 @@
+import { join } from 'path';
+import { fork } from 'child_process';
+import { Unport, Unrpc, ChannelMessage } from '../../lib';
+import { ParentPort } from './port';
+
+// 1. Initialize a port
+const parentPort: ParentPort = new Unport();
+
+// 2. Implement a Channel based on underlying IPC capabilities
+const childProcess = fork(join(__dirname, './child.js'));
+parentPort.implementChannel({
+  send(message) {
+    childProcess.send(message);
+  },
+  accept(pipe) {
+    childProcess.on('message', (message: ChannelMessage) => {
+      pipe(message);
+    });
+  },
+  destroy() {
+    childProcess.removeAllListeners('message');
+    childProcess.kill();
+  },
+});
+
+// 3. Initialize a rpc client from port.
+const parentRpcClient = new Unrpc(parentPort);
+
+parentRpcClient.implement('getInfo', request => ({
+  user: `parent (${request.id})`,
+}));
+parentRpcClient.port.postMessage('syn', { pid: 'parent' });
+parentRpcClient.port.onMessage('ack', async payload => {
+  console.log('[parent] [event] [ack] [result]', payload);
+  const response = await parentRpcClient.call('getChildInfo', {
+    name: 'parent',
+  });
+  console.log('[parent] [rpc] [getChildInfo] [response]', response);
+  setTimeout(() => {
+    console.log('destroy');
+    parentPort.destroy();
+  }, 1000);
+});

examples/child-process-rpc/port.ts

@@ -0,0 +1,30 @@
+/* eslint-disable camelcase */
+import { Unport } from '../../lib';
+
+export type Definition = {
+  parent2child: {
+    syn: {
+      pid: string;
+    };
+    getInfo__callback: {
+      user: string;
+    };
+    getChildInfo: {
+      name: string;
+    }
+  };
+  child2parent: {
+    getInfo: {
+      id: string;
+    };
+    getChildInfo__callback: {
+      clientKey: string;
+    };
+    ack: {
+      pid: string;
+    };
+  };
+};
+
+export type ChildPort = Unport<Definition, 'child'>;
+export type ParentPort = Unport<Definition, 'parent'>;

package.json

@@ -20,8 +20,8 @@
     "build": "run-s build:cjs build:esm build:example",
     "dev:cjs": "npm run build:cjs -- --watch",
     "dev:esm": "npm run build:esm -- --watch",
-    "build:cjs": "tsc -p tsconfig.json --module commonjs --outDir lib",
-    "build:esm": "tsc -p tsconfig.json --module ES2015 --outDir esm",
+    "build:cjs": "tsc -p tsconfig.src.json --module commonjs --outDir lib",
+    "build:esm": "tsc -p tsconfig.src.json --module ES2015 --outDir esm",
     "dev:example": "tsc -p tsconfig.examples.json --watch",
     "build:example": "tsc -p tsconfig.examples.json",
     "prepublishOnly": "npm run build",