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
I've seen a few servers start to serve a mount from a prezipped file system. This means only non-compressed connections get the performance hit on decompression and the website is much easier to deploy as a single zip. (possibly even appended to the app binary for even easier transport...) This could be very useful for IoT use cases...
It should be pretty easy to build this. I've not gone too far out of my way to make NNG an ideal web server -- its not intended to replace NGINX or something like that. It offers the ability most to supplement it's real purpose, which is supporting both the nanomsg protocols and embedded REST style servers (where there is dynamic content or work done rather than just serving up just a bunch of static content.) The idea is that you might want to serve up a JavaScript web page or some supporting content to go with that API.
Today there is no compression algorithm in NNG at all, so this would also mean expanding its set of dependencies.
I didn't realize there is no compression. That is probably still something you want. Compression on binary streams can be very helpful...
As far as replacing Nginx I think that serving static files with some sort of zero copy sendfile() style response system will suffice for must use cases to replace NGinx. You already use an evented design pattern so it should be comparable. Adding compression would make it a full drop-in for most every cases.
I've seen a few servers start to serve a mount from a prezipped file system. This means only non-compressed connections get the performance hit on decompression and the website is much easier to deploy as a single zip. (possibly even appended to the app binary for even easier transport...) This could be very useful for IoT use cases...
Here's how LWS handles it...
The text was updated successfully, but these errors were encountered: