Remoting layer

[gfx-rs]

Remoting layer

[kvark]

No, the native part doesn't need to know about remoting (I hope!).
We can start it by just sending messages across ipc_channel. One of the first steps would be to send over whole passes instead of individual commands.

[grovesNL]

What would the remoting layer need to contain to support this? Does wgpu-native need to be aware whether IPC is being used?

[kvark]

(copied from gitter) The way I see it working is:

• wgpu-remote will create client and server parts, linked by an actual IPC channel (or multiple of them - up to implementation details)
• the client side will expose C-API entry points to be called by Gecko bindings (on script/content side). These can actually match the APIs we expose to native, which is kinda weirdly need but not required.
• the server side will listen for IPC and do actual calls into wgpu-native

[kvark]

The infrastructure is there. It's up for discussion and changes, but it's no longer in the theoretical stage.