Jake McGinty

Why? It seems like if you set the message on a progress bar, that should be the message that's displayed?

Lol, thumbs down. Ouch. Yeah, I get what you're saying, but the underlying issue around that seems like an architectural challenge of either having a transactional API or having an...

The normal `Transport` maintains a counter that must be atomically increased such that a counter isn't reused for two messages, which would be catastrophic. The `StatelessTransport` mode, however, delegates the...

@zserik `StatelessTransportState` is not clone-able, so must currently live within an `Arc` for multi-threading workloads, which is of course not ideal since there's nothing theoretically limiting it from being the...

Yes excuse me, thank you for the correction!

Hmm, I definitely understand the usefulness of having this type of function, but I'm not yet convinced this is the right way to make it happen - while I appreciate...

Hey @delbonis! Yeah, the maximum payload size for transport messages should really be exposed in the API, good point. True that it'd be nice to have a convenience method for...

@vks I think we'd need `impl Trait` to extend support for being used in structs, which it currently can't do and I'm not sure what the roadmap is for that....

related to #62

@isislovecruft yep, it's purely for ergonomic reasons. I'd love to use something like associated traits and maybe a convenience macro to be able to drop the `Box`es while keeping roughly...