Our module must run after the Lua module for the ongoing refactor of the Lua bridge. When the Lua module postpones its handlers, we postpone ours as well. This behavior assumes ngx_wasmx_module is declared after ngx_http_lua_module during compilation (static or dynamic). This could be enforced in the future in dynamic builds, and caught at runtime with a warning for static builds.
Our module must run after the Lua module for the ongoing refactor of the Lua bridge. When the Lua module postpones its handlers, we postpone ours as well. This behavior assumes ngx_wasmx_module is declared after ngx_http_lua_module during compilation (static or dynamic). This could be enforced in the future in dynamic builds, and caught at runtime with a warning for static builds.
TODO