Jon Chambers

> This also introduces the drawback of breaking source compatibility when using Netty extensions. For example, in my project, I had to rename the import of Netty's Future. I'm not...

…and, much more importantly, thank you for the contribution!

Interesting. Yeah, the other (worse?) case would be that something _else_ has Netty on the classpath, so the `import io.netty.util.concurrent.Future` thing would still work and risk mixing/matching versions in a...

Ohhhhh yeah. Classifiers. Forgot about those ;) Cool. I'll definitely have to do some prodding to get the deployment process right, but I think we're on the right track. Thanks...

> …I think the only way to do this properly is to update Pushy API to completely hide Netty. I'm coming to the same conclusion, but am worried that the...

Some new upstream developments on the shading front: - https://github.com/netty/netty-tcnative/pull/382/ - https://github.com/netty/netty/issues/7272 - https://github.com/netty/netty/pull/6995

> `io.netty.util.concurrent.Future`, which notably allows users to attach listeners to futures. Deriving from that is the set of ...FutureListener interfaces. My enthusiasm for reinventing that set of wheels is a...

> We might be able to use `CompletableFuture` for all public methods… This is covered in #757.

I'm starting in on some initial design work for this feature, and we're going to have to work around a few obstacles. The main ones right now are: 1. We...

Oh, right, and to close out this thought: > Based on an X509 certificate's metadata, we can identify the APNs topics for which it can be used. We can't tell...