Doing a massive refactoring

[pimeys]

Hey,

I forked your repo last summer to fit it to our company's infrastructure. I was breaking lots of things and doing some things differently. We've been using my fork since the summer and now you can also use the JWT tokens for sending notifications. My plan is to clean the fork, write proper documentation and do a big pull request at some point.

Are you still maintaining this, can we release a new version at some point?

https://github.com/pimeys/apns2

Cheers,
Julius

[polyitan]

Hi,

Nice to hear that. It's cool. Yes, I still maintaining this project.
I wanted to publish this lib on Cargo repo. But for now I cant, because "solicit" still use old version OpenSSL. Also, in my plans was add simple comand line app , and support JWT tokens.
So, pull requests are welcome!

[pimeys]

I forked solicit and changed it to use 0.7 openssl which works for our own case. My fork also supports JWT now and I'm currently writing the documentation and honing the api a bit so it's good to publish.

The plan should be to get rid of solicit asap. There's a library[0] to follow and when it's ready, solicit needs to go!

The biggest problem there is that I use my own fork of solicit and the other is dependency to btls library, which is not published yet.

https://github.com/lambdastackio/tokio-http2

[pimeys]

Oh, and I wrote couple of examples which you can use to fire pushes from command line :)

https://github.com/pimeys/apns2/tree/master/examples

[pimeys]

One thing that is tricky with this is how to write tests. Even integration tests are a massive PITA because you must mock the connection to APNs somehow with the right certificates and so on. That's why we wanted to do our push system with Rust, that we don't need so many tests to get things to production.