3 ms·
Waiting for first guy who take this implementation and run it through emscripten so we can actually use it in client -> server communication, eg sending compre
by finchisko 10y ago
Waiting for first guy who take this implementation and run it through emscripten so we can actually use it in client -> server communication, eg sending compressed json payloads to the server.
- panic 10y agoIs running (not to mention downloading/parsing/compiling) emscriptened decompression code really that much faster than just transferring the data? I think a better strategy would be to add support for LZFSE to the browsers themselves.
- finchisko 10y agoNative support in browser would be appreciated. But I was also thinking about nodejs server side decompressing via native or emscripten transpiled module.
- ascagnel_ 10y agoA quick reading of the license[0] shows that there's no legal stumbling blocks to the code showing up in browsers, but the license doesn't mention anything about patents. [0] https://github.com/lzfse/lzfse/blob/master/LICENSE https://github.com/lzfse/lzfse/blob/master/LICENSE
- finchisko 10y agoIt would be slower, but point is to reduce bits when sending large json over cellular network.
- madeofpalk 10y agoYou mean... like gzip?
- finchisko 10y agoyeah, but also the opposite direction client -> server. client will send compressed data to server use LZFSE. Kind of nice extension to HTTP protocol, which only supports compression from server to client.
- Twirrim 10y agoThere are already gzip, lzma etc. compression libraries for javascript you could use if you really wanted to do this.