Thanks Joe. You are correct, this initial implementation is the simplest one to get it off the ground. We plan to continue development and add the streaming functionality, which we know we will need for things like large PDF file generation or support for Proxy-Wasm.
Yes, isolating language runtimes (PHP, Python, ...) per thread is a cool feature that enables new possibilities like simultaneously supporting multiple versions of PHP as well as better multi-tenancy (you will be able to keep user's code and assets separate from each other using Wasm built-in isolation mechanism). Regarding apreq, right now we have not had a need to use it as we pass most of the headers and body to the runtimes themselves as the language runtimes code for handling requests, etc. takes care of it as part of the CGI implementation, etc. As we look to add different functionality (i.e. extending Apache itself) we will probably provide access to it from Wasm. De: Joe Schaefer <j...@sunstarsys.com> Responder a: "dev@httpd.apache.org" <dev@httpd.apache.org> Fecha: jueves, 26 de enero de 2023, 5:17 Para: "dev@httpd.apache.org" <dev@httpd.apache.org> Asunto: Re: mod_wasm: Contributing Upstream to Apache Still, the idea is wicked cool if mod_wasm really can isolate the Python, PHP, etc targets onto individual POSIX threads. Very exciting stuff for HTTP/2 Webapps.
