alexsdsr

Hello @swcurran . I've created a PR (https://github.com/hyperledger/aries-cloudagent-python/pull/2540) that could become a start point in the discussion about `please_ack` support in ACA-Py. I would appreciate if someone takes a look...

> Thanks! Awesome. Sorry for the silence on this — we’ve been at a conference this week. We’ll be looking at this next week. Would you be willing to present...

created a PoC (https://github.com/hyperledger/aries-cloudagent-python/pull/2546) for the `option 2` described in the document provided by this PR.

> Outstanding document and assessment. Great work! Sorry it has taken so long for feedback. > > I agree with your assessment on the options, and that 2 and 3...

> After reviewing the [0317 Please Ack RFC](https://github.com/hyperledger/aries-rfcs/tree/main/features/0317-please-ack) and your excellent investigation into the protocol and the state of ACA-Py, here are my comments and suggestions: > > 1. I...

Hello @swcurran. There are some answers and questions below. > If we have to track each message, I think it is much more complicated Since the `please_ack` RFC is not...

Hello @swcurran > We can talk it to the Aries community, but I would say that we should go with protocol OUTCOME only. Have you had a chance to discuss...

Hello @swcurran. Thank you for the answer. > flag that a “please_ack” is needed at whatever is defined to be the next “outcome” — presumably the next state change. At...

Hello @swcurran > The most important thing is how not to lose this information you have learned. Closing these PRs without put the learning some where would be a bad...

Hello @swcurran Could you please take a look at the final version of the document? Is it worth having it in the repo? What do you think? Thank you.