Joel Berger

Oh, it seems I misremembered the previous functionality. I had thought it would preserve the whole chain but the query does not appear to be so https://github.com/mojolicious/minion/commit/cb9182acc83938ac46ee6227e4e9d914eb56cf28

I agree with @Grinnz, the start event is all you need. There is no distinction between sync and async requests in the event system. Actually, under the hood even "blocking"...

Oh, I think I meant prepare: https://docs.mojolicious.org/Mojo/UserAgent#prepare . I remember when prepare was added, it was specifically meant to be before anything happened in order to allow url rewriting. In...

No, I now see the problem, I was (stupidly) thinking about the use-case of trying to hit a private IP by IP not by DNS name. Honestly I don't think...

Here you can see how NDN is used to resolve in a non-blocking way and clearly then we'd have the address but if you don't use that IO::Socket::IP just does...

I feel like the easiest way might be to have per-transaction socket options which get merged into the global ones that come from Mojo::UserAgent. That would allow you to do...

These would make an excellent plugin. I don't believe they would be a good fit for core.

Could it also implement `can_ping` with a default implementation of `return 0`? Then backends can choose to implement or not. Or heck the default implementation of `ping` could just assume...