-
Notifications
You must be signed in to change notification settings - Fork 916
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle IPC descriptor serialization #22
Labels
type: question
Further information is requested
Comments
Related to #146 (comment) |
Merged
bors bot
added a commit
that referenced
this issue
Oct 26, 2019
358: Remove all the IPC r=grovesNL a=kvark Closes #146 Closes #22 We have decided to use Gecko IPC for Firefox. `wgpu-remote` will therefore provide all the Rust glue that Gecko needs for client and server: - initialization/termination of client/server - ID management for the client - pass encoding blobs In Servo, we'd need to enable `serde` feature of `wgpu-native` and potentially roll out a different remoting crate that would establish a protocol based on `ipc-channel`, as we wanted originally. Co-authored-by: Dzmitry Malyshau <kvarkus@gmail.com>
bors bot
added a commit
that referenced
this issue
Oct 26, 2019
358: Remove all the IPC r=grovesNL a=kvark Closes #146 Closes #22 We have decided to use Gecko IPC for Firefox. `wgpu-remote` will therefore provide all the Rust glue that Gecko needs for client and server: - initialization/termination of client/server - ID management for the client - pass encoding blobs In Servo, we'd need to enable `serde` feature of `wgpu-native` and potentially roll out a different remoting crate that would establish a protocol based on `ipc-channel`, as we wanted originally. Co-authored-by: Dzmitry Malyshau <kvarkus@gmail.com>
bors bot
added a commit
that referenced
this issue
Oct 26, 2019
358: Remove all the IPC r=grovesNL a=kvark Closes #146 Closes #22 We have decided to use Gecko IPC for Firefox. `wgpu-remote` will therefore provide all the Rust glue that Gecko needs for client and server: - initialization/termination of client/server - ID management for the client - pass encoding blobs In Servo, we'd need to enable `serde` feature of `wgpu-native` and potentially roll out a different remoting crate that would establish a protocol based on `ipc-channel`, as we wanted originally. Co-authored-by: Dzmitry Malyshau <kvarkus@gmail.com>
bors bot
added a commit
that referenced
this issue
Oct 26, 2019
358: Remove all the IPC r=grovesNL a=kvark Closes #146 Closes #22 We have decided to use Gecko IPC for Firefox. `wgpu-remote` will therefore provide all the Rust glue that Gecko needs for client and server: - initialization/termination of client/server - ID management for the client - pass encoding blobs In Servo, we'd need to enable `serde` feature of `wgpu-native` and potentially roll out a different remoting crate that would establish a protocol based on `ipc-channel`, as we wanted originally. Co-authored-by: Dzmitry Malyshau <kvarkus@gmail.com>
RandyMcMillan
pushed a commit
to RandyMcMillan/wgpu
that referenced
this issue
Jun 19, 2024
Basic `wgpu` renderer
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Follow-up from #20:
Should we change the types of descriptors to(already done)const uint8_t *desc
(i.e. binary serialized) for the remote case in wgpu.h?The text was updated successfully, but these errors were encountered: