I try to run your extension, but i can makes work.
You should be able to clone my gist and try it out yourself. When I do profiling, it looks like the JS-Native bridge is the bottleneck with all of the network api calls, but I could be wrong. I suspect it's something to do with trying to allocate too much in the way of resources - memory, disk space, network connections, etc. It crashes either the app or the entire browser. Downloading totally legal torrents and embedding them in video tags.Downloading and seeding on the webtorrent network (it's a hybrid client!).Downloading and seeding on the bittorrent network.That just uses the net module provided by chrome-net and gets DNS resolving using the chrome APIs. It was pretty easy to find chrome-compatible modules to polyfill things like net and dgram, because already made them! I was also able to grab native-dns to polyfill dns. The hard part was aliasing all of the node-only modules and overriding browser excludes. I managed to get this working a while ago.
0 kommentar(er)
