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
gloo-worker uses post_message to send serialized messages between workers. For some messages, it might be better to use post_message_with_transfer to send partially serialized messages while avoiding expensive copies. For example, if I had a struct like
then I'd like to send this between workers by serializing the first two fields and transferring giant_array. Is this a use-case that gloo-worker is interested in supporting? The implementation I have in mind would involve custom Serialize-Deserialize-like traits and a derive macro...
(edit: I didn't mean to add the "bug" label, sorry, but it looks like I can't remove it)
The text was updated successfully, but these errors were encountered:
I've been just doing my workers "by hand" instead of using gloo-worker. I'm "serializing" my structs to javascript Arrays by hand and using post_message_with_transfer. It's a bit painful, but it's doable if you only have a couple different kinds of structs to send.
gloo-worker uses
post_message
to send serialized messages between workers. For some messages, it might be better to usepost_message_with_transfer
to send partially serialized messages while avoiding expensive copies. For example, if I had a struct likethen I'd like to send this between workers by serializing the first two fields and transferring
giant_array
. Is this a use-case that gloo-worker is interested in supporting? The implementation I have in mind would involve customSerialize
-Deserialize
-like traits and a derive macro...(edit: I didn't mean to add the "bug" label, sorry, but it looks like I can't remove it)
The text was updated successfully, but these errors were encountered: