Volker Berlin

more dependencies: * de.intarsys.opensource:jbig2_5.5.1 - CVE-2022-31548 * jakarta.servlet:jakarta.servlet-api:4.0.4 - CVE-2022-31569

> All of the browser specific APIs are already in a separate specification. The browser specific APIs are specified by the W3C: > > https://webassembly.github.io/spec/js-api/ @Pauan The request means an...

My understanding is that the suggestion is an API like WASI for a WASM runtime that run inside a browser or any other WASM runtime with a GUI. And of...

What are the **relevant** production engines today? V8, SM and JSC? Is Chakra still relevant? Which market share makes a VM relevant? This term is just as vague. Because new...

The following table shows the status of future WebAssembly features required by JWebAssembly in nightly builds in various implementations according to my tests. | Feature | V8 | SpiderMonkey |...

> Why wouldn't it support them ? The library is written in portable C In the latest release I see only binaries for x86 https://github.com/uclouvain/openjpeg/releases/tag/v2.3.1

In the meantime there is [RFC9220 Bootstrapping WebSockets with HTTP/3](https://www.rfc-editor.org/rfc/rfc9220.html).

Disabling the TLS 1.3 protocol with: > -Djdk.tls.client.protocols="TLSv1,TLSv1.1,TLSv1.2" solved the problem.

Yes, the hack does not work anymore. Today it is failing with Java 11 and Java 12.

Yes, this can be helpful for my Java implementation. It can be reduce a lot of code.