On Sunday, April 9, 2017 at 7:22:26 PM UTC-7, Kenton Varda wrote: > > On Sun, Apr 9, 2017 at 7:04 PM, Wink Saville <wi...@saville.com > <javascript:>> wrote: >> >> 2) The interface between JS and WASM would probably be very slow if every >>> accessor has to go through it. You'd probably end up wanting to translate >>> the whole capnp to a JSON object upfront, which of course defeats a lot of >>> the purpose. >>> >> >> I'm hoping shared memory >> <https://www.google.com/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=javascript+shared+memory> >> >> might be used, we could have serdes in wasm and access in JS, take with >> huge grain of salt :) >> > > But in Cap'n Proto, there is no serdes. All of the logic happens at access > time. >
Hmmm, I forgot, thinking of my old protobuf days. Anyway, one of the use cases is using is using messaging to communicate between wasm and js so if we can't share any implementation so be it. > > -Kenton > -- You received this message because you are subscribed to the Google Groups "Cap'n Proto" group. To unsubscribe from this group and stop receiving emails from it, send an email to capnproto+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/capnproto.
