This is great news for the pagespeed people.
As it stands, though, the module system would be very helpful for OS packagers, because they don't have to worry about signature mismatch.
11–20 of 63 posts
This is great news for the pagespeed people.
As it stands, though, the module system would be very helpful for OS packagers, because they don't have to worry about signature mismatch.
This is great news for the pagespeed people.
Unfortunately, it looks like it may not be something will be able to work with. Instead of an ABI like Apache uses, Nginx went with signature checking. To load a precompiled module, the signature has to match. This means we would have to compile many different binary modules for every configuration people might have, and for every version of Nginx. Like several dozen. As it stands, though, the module system would be…
Of course, serving the output would be harder, but still not impossible.
A little more explanation of what that means from the docs: In NGINX 1.9.11 onwards a new way of loading modules dynamically has been introduced. This means that selected modules can be loaded into NGINX at runtime based on configuration files. They can also be unloaded by editing the configuration files and reloading NGINX. https://www.nginx.com/resources/wiki/extending/converting/
This is great news for the pagespeed people.
Unfortunately, it looks like it may not be something will be able to work with. Instead of an ABI like Apache uses, Nginx went with signature checking. To load a precompiled module, the signature has to match. This means we would have to compile many different binary modules for every configuration people might have, and for every version of Nginx. Like several dozen. As it stands, though, the module system would be…
load webserver.nlm
(a reference for the old-timers here)Seems an odd feature for 1.9.11, why not wait for 2.0?
Good for them. It's worth to note that an nginx fork called Tengine (by Taobao) has a similar feature before. http://tengine.taobao.org/index.html
Earlier quoted context omitted.
Unfortunately, it looks like it may not be something will be able to work with. Instead of an ABI like Apache uses, Nginx went with signature checking. To load a precompiled module, the signature has to match. This means we would have to compile many different binary modules for every configuration people might have, and for every version of Nginx. Like several dozen. As it stands, though, the module system would be…
So does nginx still have to know about all of the modules at compile-time? Or can I compile nginx, then later compile a module for that nginx?
(But I'd really love a way to distribute binary modules anyone could just use, with no additional compilation.)
http://nginx.org/en/docs/http/ngx_http_stub_status_module.ht...