Re: Re: mod_wasm: Contributing Upstream to Apache

2023-01-27 Thread Joe Schaefer
Part of the really cool things you'd like to have as an app-server author that knows the APR/APU/HTTPd runtime are subrequests, including the portions that interact with the filter API. I'm always writing home-grown app-specific SSI-ish filters via mod_perl to process application pages as

Re: mod_wasm: Contributing Upstream to Apache

2023-01-27 Thread Joe Schaefer
Looking over the WASM Roadmap, it appears that they have a plan for multithreading within a single target language. That would allow you to fully support every silly GIL-addled language runtime out there, which would be very compelling. On Fri, Jan 27, 2023 at 1:33 PM Joe Schaefer wrote: > A

Re: mod_wasm: Contributing Upstream to Apache

2023-01-27 Thread Joe Schaefer
A native interface outside of CGI compat for apreq would be a killer new feature, because it really finishes our vision for apreq as the one-HTML-spec-parser for all native apps, regardless of language choice. Of course this would be a new opt-in feature for target languages to take advantage of,

Re: mod_wasm: Contributing Upstream to Apache

2023-01-27 Thread Jesús González
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

RE: Re: mod_wasm: Contributing Upstream to Apache

2023-01-27 Thread Jesús González
Hi Eric, Thanks for the feedback. Though Wasm is relatively new it is being adopted by other HTTP-related projects, like NGINX and Envoy proxy and even ASF projects like APISIX. We want to contribute upstream to bring some of these new features to the Apache web server, similarly to how we are

Re: svn commit: r1907031 - /httpd/httpd/trunk/docs/manual/mod/mod_proxy.xml

2023-01-27 Thread Yann Ylavic
On Fri, Jan 27, 2023 at 4:41 PM Eric Covener wrote: > > maybe we can duplicate that in the "basic examples" at the top of the page? Good point, did that in r1907035 (and linking to it in the note rather than copying the same example). I also added a deprecation warning to mod_proxy_wstunnel

Re: svn commit: r1907031 - /httpd/httpd/trunk/docs/manual/mod/mod_proxy.xml

2023-01-27 Thread Eric Covener
maybe we can duplicate that in the "basic examples" at the top of the page? On Fri, Jan 27, 2023 at 10:31 AM wrote: > > Author: ylavic > Date: Fri Jan 27 15:30:46 2023 > New Revision: 1907031 > > URL: http://svn.apache.org/viewvc?rev=1907031=rev > Log: > docs: Better mod_proxy_wstunnel vs