Stream: git-wasmtime

Topic: wasmtime / issue #7276 wasi-http: does the response-outpa...

Wasmtime GitHub notifications bot (Oct 17 2023 at 23:04):

elliottt opened issue #7276.

Wasmtime GitHub notifications bot (Oct 17 2023 at 23:05):

elliottt assigned issue #7276 to lukewagner.

Wasmtime GitHub notifications bot (Oct 17 2023 at 23:05):

elliottt edited issue #7276:

We could always set a response that has an appropriate error code and body, why do we allow writing a result<response, error>?

Wasmtime GitHub notifications bot (Oct 18 2023 at 15:24):

lukewagner commented on issue #7276:

IIUC (not 100% sure here but...), there is a meaningful difference between an error (status) code inside a response (which, I believe is meant to come from the origin) and an error code that you get instead of getting a response (which represents an error somewhere along the path). Symmetrically, this matches the result<incoming-response, error> and the result<future-incoming-response, error> for outgoing-handler.

Wasmtime GitHub notifications bot (Oct 24 2023 at 16:27):

elliottt commented on issue #7276:

I think that makes sense: giving the embedder the option ability to respond differently to those errors seems right.

Wasmtime GitHub notifications bot (Oct 24 2023 at 16:27):

elliottt closed issue #7276:

We could always set a response that has an appropriate error code and body, why do we allow writing a result<response, error>?

Last updated: Nov 22 2024 at 16:03 UTC