Add Remote API to Support In-Process, Multi-Process, and Network Rendering

[adamjs]

For various reasons (crash recovery, site isolation, asynchronous rendering), certain users may wish to run the Renderer/Views in a standalone process.

Build a multi-process RPC layer around the C API so users can start and run multiple, independent instances of the library.

[adamjs]

The plan for this has changed-- we're now adding a Remote (RPC) Layer on top of our core API via Protocol Buffers and ZeroMQ.

This new Remote API will support several things:

Remote Rendering:

• In-Process Rendering (separate thread)
• Multi-Process Rendering (separate process(es))
• Network Rendering (streamed over socket)

Improved Security (for platforms that support multi-process):

• Isolate insecure content in separate processes
• Isolate crashed or stalled Views

Multi-Language Bindings

• Allow us to support language bindings more effectively.
• Protocol Buffers have generators for C#, Rust, Lua, Dart, Go, Java, Kotlin, Objective-C, Python, and Ruby. The compiler (protoc) can be extended to generate code for more targets.

[JailbreakPapa]

@adamjs Hey, any update on this?