spec

spec copied to clipboard

HTTP: add ability to return early / skip future callbacks

3

(This is somewhat related to #63, not sure if it's better to fold into that or keep as a separate issue) ext_proc filter supports the notion of a [processing mode...

mpwarres

Consistent style in the ABI (expanded vs minimal)

1

During the initial development, we went through a lot of back-and-forth both expanding and minimizing the ABI surface (e.g. `get_buffer_bytes(buffer_type)` vs `get_http_request_body_chunk()` and similar, `set_shared_data(NULL)` vs `remove_shared_data()`), both internally and...

PiotrSikora

Crypto extensions

1

What's the strategy with respect to cryptographic primitives in the ABI? Envoy currently exposes `verify_signature` as a foreign function because some customers need FIPS certification. Do we recommend using boringssl...

kyessenov

Make it clear what text encoding string values are expected to be in.

3

I got feeling it's likely UTF8, but would be nice if the spec made that clear.

chirino

Unique identifiers of worker contexts in multithreaded environment

2

Following сomment relates to Envoy proxy (I don't know much about other proxy-wasm implementations). Multi-threaded servers may use separate WASM runtime for each worker thread. At least in Envoy identifiers,...

vchigrin

ABI v0.3.0 scope & tracking issue

2

There are 3 groups of features that I believe should be addressed and implemented as part of ABI v0.3.0: Fixes for well-known and outstanding issues: - [ ] support multiple...

PiotrSikora

Per discussion in https://github.com/envoyproxy/envoy/pull/36809

kyessenov

Remove `plugin_context_id` from callbacks.

3

PiotrSikora

PiotrSikora

Add support for host features.

1

The `proxy_get_host_features` hostcall can be used by the SDKs to determine which features are supported by the host environment.

PiotrSikora