Ah, I see now. Thanks for going deeper on that.
I did eventually find the RPC stuff for Go, and thought that that might be
interesting to implement.
On Tue, Dec 29, 2009 at 8:31 AM, Joan Miller wrote:
> "Each component runs in its own private address space. Inter-component
> communication is b
"Each component runs in its own private address space. Inter-component
communication is based on Native Client’s reliable datagram service,
the IMC (Inter-Module Communications). For communications between the
browser and a NaCl module, Native Client provides two options: a
Simple RPC facility (SRP
I guess I'm confused by what it means to "support" this in a language.
My understanding is this is using lightweight virtualization technology
(perhaps via segment register hacks on x86, and something else on ARM) to
provide a safe sandbox to run native code in a browser. If I had to guess,
I'd s
Native CLient (NaCl) [1] is a technology very cool which lets to run
native code in web applications, and it's being integrated in some
languages as Python [2]. Go [3] already has rudimentary support for
Native Client (and it's logical since that both technologies are from
Google)
I hope that Hask
