You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To support deeper platform integration with native OS features and browser extensions we need an IPC framework that can accept messages, handle them and reply.
Message encoding will use protobuf for consistency with other parts of the code base.
Components
Listener to be embedded in the GUI app will receive messages and execute them in the context of an account (using the webassembly runtime)
Client to communicate with the listener
Bridge executable for browser extensions (native messaging)
Webassembly runtime to sandbox code execution and eventually allow third-party extensions to the app functionality
The IPC framework will likely only be applicable to desktop platforms but the webassembly runtime and sandbox would allow us to share logic with the mobile platforms.
For ios which does not allow dynamic code execution we can bundle the wasm files into the app.
To support deeper platform integration with native OS features and browser extensions we need an IPC framework that can accept messages, handle them and reply.
Message encoding will use protobuf for consistency with other parts of the code base.
Components
The IPC framework will likely only be applicable to desktop platforms but the webassembly runtime and sandbox would allow us to share logic with the mobile platforms.
For ios which does not allow dynamic code execution we can bundle the wasm files into the app.
Libraries
Some candidates for IPC libraries we can use:
Integrations
The text was updated successfully, but these errors were encountered: