minghuaw
minghuaw
In the current implementation, `DeliveryInfo::from(&delivery)` will clone the delivery info carried in the `delivery`. A `Cow` could probably be used to avoid this cloning. However, this is potentially a breaking...
The remote peer could reject the resumption by replying an `Attach` with empty `source` and empty `target` fields.
This would be something similar to `quinn-proto`
#170 > Upon receiving a transfer, the receiving endpoint will increment the next-incoming-id to match the implicit transfer-id of the incoming transfer plus one, as well as decrementing the remote-outgoing-window,...
> ## 2.2 Client Model > > This document does not define either an authentication or authorization protocol nor does it impose any restrictions on protocol choices other than requiring...
Support parsing the whole body section as a raw bag of bytes. This will require change in `serde_amqp`
> Note that a null value and a zero-length array (with a correct type for its elements) both describe an absence of a value and MUST be treated as semantically...
Is it expected that the user need to add `wit` files of secondary dependencies into `Cargo.toml`? For example, in this modified tutorial example (https://github.com/minghuaw/wasm-component-tutorial), `package component:calculator` imports `component:add/add` and `component:sub/sub`,...