In my application I've seen using Contexts to communicate cancellation, and from what I can tell there's not a way to incorporate this into this project's API, even with workarounds. In other places I've been able to work around this by setting a deadline for open connections to cancel in-progress requests, but the API of this project does not expose Conn objects either. For now I can just set my timeouts to be shorter than necessary to sort of work around this, but it would be helpful if I could use contexts, or at least work around this by accessing the raw Conn objects.
It also seems to me that this would provide ways to resolve issue #62.
In my application I've seen using
Contexts to communicate cancellation, and from what I can tell there's not a way to incorporate this into this project's API, even with workarounds. In other places I've been able to work around this by setting a deadline for open connections to cancel in-progress requests, but the API of this project does not exposeConnobjects either. For now I can just set my timeouts to be shorter than necessary to sort of work around this, but it would be helpful if I could use contexts, or at least work around this by accessing the rawConnobjects.It also seems to me that this would provide ways to resolve issue #62.