deno-amqp
deno-amqp copied to clipboard
lenkan
In Deno it is now possible to use mTLS Thanks to the `certChain` and `privateKey` parameters in the unstable API of the connectTLS method. Read more: https://deno.land/[email protected]?s=Deno.ConnectTlsOptions&unstable=. Please consider adding...
feat: Provide a DeliveryMode enum to make clear the choices allowed by the AMQP spec (i.e. 0 or 1)
In relation to https://github.com/lenkan/deno-amqp/issues/41, this should make it more clear what is allowed for the DeliveryMode enum.
When the socket receives a bad frame during a read, it should raise a connection error by sending a `connection.close` frame and wait for the `connection.close-ok` before closing the socket....
It just creates a lot of noise: https://doc.deno.land/https/deno.land/x/amqp/mod.ts For example, only BasicProperties actually has a non-empty shape, so all other property interfaces can be omitted during the codegen.
basic.get is the only AMQP method that can have two different response methods. The codegen currently does not handle this well, especially since basic.get-ok carries content and basic.get-empty does not....
## summary * change Deno.Writer / Reader / Closer and its sync type to std https://github.com/denoland/deno/issues/9795 * rework BufReader to buf.read https://github.com/denoland/std/pull/6056 * use deno.json * fix #47
