Re: mod_wasm: Contributing Upstream to Apache

imited > interfaces to the Wasm binary to perform such actions. So yes, we believe > your proposal of getting the apreq_* (ARP table-based) interfaces exposed > as read-only data structures is doable and useful. > > Cheers! > > > > *De: *Joe Schaefer > *Fecha: *miérc

Re: mod_wasm: Contributing Upstream to Apache

Schaefer Fecha: miércoles, 5 de julio de 2023, 4:59 Para: dev@httpd.apache.org Asunto: Re: mod_wasm: Contributing Upstream to Apache !! External Email The win with having an apr table api from httpd is that by sharing those tables in the sandbox, various programming languages will be able to interact

Re: mod_wasm: Contributing Upstream to Apache

he Enterprise Jamstack Wiki* > > -- > *From:* Jesús González > *Sent:* Monday, July 3, 2023 8:49:33 AM > *To:* dev@httpd.apache.org > *Subject:* Re: mod_wasm: Contributing Upstream to Apache > > > Hola! > > mod_wasm v0.12.1 > <https://github.com/vmware-labs/mod_w

Re: mod_wasm: Contributing Upstream to Apache

Wiki From: Jesús González Sent: Monday, July 3, 2023 8:49:33 AM To: dev@httpd.apache.org Subject: Re: mod_wasm: Contributing Upstream to Apache Hola! mod_wasm v0.12.1<https://github.com/vmware-labs/mod_wasm/releases/tag/v0.12.1> is now ava

Re: mod_wasm: Contributing Upstream to Apache

, 2 de junio de 2023, 19:09 Para: dev@httpd.apache.org Asunto: Re: mod_wasm: Contributing Upstream to Apache Thanks Joe for your encouragement! And yes, your feedback was what inspired us to expand mod_wasm in this direction. In the demo from my colleague Asen, we expose three wrapper fun

Re: mod_wasm: Contributing Upstream to Apache

our feedback. De: Joe Schaefer Fecha: jueves, 1 de junio de 2023, 22:16 Para: dev@httpd.apache.org Asunto: Re: mod_wasm: Contributing Upstream to Apache !! External Email Huge fan, love that you are receptive to my feedback. If you get to the point where the apreq_* (APR table-based) interfa

Re: mod_wasm: Contributing Upstream to Apache

rom Wasm. >> >> >> >> >> >> *De: *Joe Schaefer >> *Responder a: *"dev@httpd.apache.org" >> *Fecha: *jueves, 26 de enero de 2023, 5:17 >> *Para: *"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. >> >

Re: mod_wasm: Contributing Upstream to Apache

fferent functionality (i.e. > extending Apache itself) we will probably provide access to it from Wasm. > > > > > > *De: *Joe Schaefer > *Responder a: *"dev@httpd.apache.org" > *Fecha: *jueves, 26 de enero de 2023, 5:17 > *Para: *"dev@httpd.apache.org" &

Re: mod_wasm: Contributing Upstream to Apache

Huge fan, love that you are receptive to my feedback. If you get to the point where the apreq_* (APR table-based) interfaces in trunk can be exposed as read-only data structures in mod_wasm as an optional API for power httpd users that like the sandboxed functionality you get OOTB, that would

Re: mod_wasm: Contributing Upstream to Apache

I think not making WASM a first class concern in a proxy or server is missing out, more so in those platforms where extensibility isn't trivial. Apache will remain running in current setups but having limited extensibility is something concerning these days as systems are getting more and more

Re: mod_wasm: Contributing Upstream to Apache

Hola! We just released a mod_wasm security update (v0.11.2) to address a recent CVE (low security). More details in the changelog. Cheers, Jesús

Re: mod_wasm: Contributing Upstream to Apache

Hola! We have released recent versions of mod_wasm allowing Wasm modules to return any output type via stdout, including binaries with non UTF-8 bytes sequences or \0 NULL terminators in the middle, among other fixes (see

Re: mod_wasm: Contributing Upstream to Apache

Great! Thanks Steffen.

Re: mod_wasm: Contributing Upstream to Apache

Done, version 0.10.3 available on the VS17 download page. Cheers, Steffen On Thursday 09/03/2023 at 16:34, Jesús González wrote: Hola! We just released a mod_wasm security update (v0.10.3) to address two recently disclosed CVEs (one critical) of Wasmtime, the WebAssembly runtime

Re: mod_wasm: Contributing Upstream to Apache

Hola! We just released a mod_wasm security update (v0.10.3) to address two recently disclosed CVEs (one critical) of Wasmtime, the WebAssembly runtime mod_wasm uses. Further details can be found in this

Re: mod_wasm: Contributing Upstream to Apache

Yes, the usage of Wasm for filters makes a lot of sense. This is why I previously mentioned the Envoy’s proxy-wasm spec, which is essentially an ABI specification for running WebAssembly in proxies. Beyond Envoy, you can find similar approaches in

Re: Re: mod_wasm: Contributing Upstream to Apache

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

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

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

Apache itself) we will probably provide access to it from Wasm. De: Joe Schaefer Responder a: "dev@httpd.apache.org" Fecha: jueves, 26 de enero de 2023, 5:17 Para: "dev@httpd.apache.org" Asunto: Re: mod_wasm: Contributing Upstream to Apache Still, the idea is wicked cool if

RE: Re: mod_wasm: Contributing Upstream to Apache

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: mod_wasm: Contributing Upstream to Apache

om:* Joe Schaefer > *Sent:* Tuesday, January 24, 2023 4:06:13 PM > *To:* dev@httpd.apache.org > *Subject:* Re: mod_wasm: Contributing Upstream to Apache > > Would be great to marry it to apreq, too. > > On Tue, Jan 24, 2023 at 4:04 PM Joe Schaefer wrote: > > It is imp

Re: mod_wasm: Contributing Upstream to Apache

From: Joe Schaefer Sent: Tuesday, January 24, 2023 4:06:13 PM To: dev@httpd.apache.org Subject: Re: mod_wasm: Contributing Upstream to Apache Would be great to marry it to apreq, too. On Tue, Jan 24, 2023 at 4:04 PM Joe Schaefer mailto:j...@sunstarsys.com>>

Re: mod_wasm: Contributing Upstream to Apache

Would be great to marry it to apreq, too. On Tue, Jan 24, 2023 at 4:04 PM Joe Schaefer wrote: > It is impossible to run mod_h2 without it or similar. > > On Tue, Jan 24, 2023 at 3:37 PM Eric Covener wrote: > >> > We are still very interested in contributing this module upstream and >> helping

Re: mod_wasm: Contributing Upstream to Apache

It is impossible to run mod_h2 without it or similar. On Tue, Jan 24, 2023 at 3:37 PM Eric Covener wrote: > > We are still very interested in contributing this module upstream and > helping to maintain it. Please, let us know what improvements or changes > would be needed for it to be

Re: mod_wasm: Contributing Upstream to Apache

> We are still very interested in contributing this module upstream and helping > to maintain it. Please, let us know what improvements or changes would be > needed for it to be considered ready for inclusion. As a pessimistic PMC member not caring about WASM or these languages, I worry that

Re: mod_wasm: Contributing Upstream to Apache

Hola! I wanted to update you on our progress since we have recently published new WebAssembly builds for several language runtimes, including: - PHP 8.1.11 and 8.2.0 - Python 3.11.1 - Ruby 3.2.0 With the inclusion of multi-module support in the mod_wasm v0.10.0 release, Apache can now serve

Re: mod_wasm: Contributing Upstream to Apache

Hola! Did anyone have the chance to take a look to the latest PR? It would be great to receive any additional feedback with the upstream contribution in mind. We are making great progress in our end, now focused on porting more PHP apps for mod_wasm, and support for new language runtimes such

FW: mod_wasm: Contributing Upstream to Apache

Hi everyone, A couple of good news. First, now mod_wasm and its dependency wasm_runtime are successfully built as part of a new test in Travis CI: https://app.travis-ci.com/github/apache/httpd/jobs/591640483 The changes have been added to the open PR #335:

Re: mod_wasm: Contributing Upstream to Apache

Thanks, Ruediger! mod_wasm code can be reviewed now on the PR: https://github.com/apache/httpd/pull/335 I will work on adding a Travis CI test for mod_wasm. Cheers, Jesús El 13/12/22, 20:45, "Ruediger Pluem" mailto:rpl...@apache.org>> escribió: !! External Email On 12/13/22 7:58 PM, Jesús

Re: mod_wasm: Contributing Upstream to Apache

On 12/13/22 7:58 PM, Jesús González wrote: > Thank Jean-Frederic for your feedback! > > Regarding reviewing from the diff, I agree that a PR to GitHub will ease the > review process. > I'm afraid I don't have enough permission to do it. Who/where can I ask for > it? You don't need special

Re: mod_wasm: Contributing Upstream to Apache

Thank Jean-Frederic for your feedback! Regarding reviewing from the diff, I agree that a PR to GitHub will ease the review process. I'm afraid I don't have enough permission to do it. Who/where can I ask for it? On the issue with wasm_return_const_char_ownership(), that's probably because we

Re: mod_wasm: Contributing Upstream to Apache

On 11/14/22 07:37, Jesús González wrote: Hi everyone, I’m Jesús González, and I am part of VMware’s Wasm Labs: wasmlabs.dev , a group focused on creating open source tools for WebAssembly. We have created mod_wasm, an Apachemodule for running WebAssembly binaries

Re: mod_wasm: Contributing Upstream to Apache

Thanks for your feedback, Christophe! We have addressed all these different issues in our repo: - All logging is now properly route to `ap_log_error()`, `ap_log_perror()` and `ap_log_rerror()`. - Also now using APLOG_MARK, and all errors marked as APLOG_ERR. - Removed unused code in

Re: mod_wasm: Contributing Upstream to Apache

*Fecha: *lunes, 14 de noviembre de 2022, 7:38 *Para: *"dev@httpd.apache.org" *CC: *Daniel Lopez Ridruejo *Asunto: *mod_wasm: Contributing Upstream to Apache Hi everyone, I’m Jesús González, and I am part of VMware’s Wasm Labs: wasmlabs.dev <https://nam04.safelinks.protection.outlook.

Re: mod_wasm: Contributing Upstream to Apache

Hi everyone, We have just posted a new article about mod_wasm v0.10.0 and published a new container to try different mod_wasm demos in two simple

Re: mod_wasm: Contributing Upstream to Apache

know if you have questions or suggestions. > > Jesús > > > > PS: Updated patch attached. > > > > > > *De: *Jesús González > *Responder a: *"dev@httpd.apache.org" > *Fecha: *lunes, 14 de noviembre de 2022, 7:38 > *Para: *"dev@httpd.apache.org&

mod_wasm: Contributing Upstream to Apache

Hi everyone, I’m Jesús González, and I am part of VMware’s Wasm Labs: wasmlabs.dev, a group focused on creating open source tools for WebAssembly. We have created mod_wasm, an Apache module for running WebAssembly binaries inside httpd, and we would like to contribute