`a2::response::Response` is confusing. about a2 HOT 2 CLOSED

Hi,

It's been a while since I've worked with apple notifs and our company is no more. So I need to think a bit how my reasoning was here...

Our notification consumer is now also open source and here you see me mapping the errors:
https://github.com/xray-tech/xorc-notifications/blob/master/src/apns2/consumer.rs#L127

• Ok is a successful notification and we don't do anything.
• Err(Error::ResponseError(e)) is an error from apple while processing the notification.
• Err(e) is an error that happened while connecting or transferring data. Something that is fatal.

Might not be so kosher anymore in 2019, but now if we're breaking the API, could you write a pull request as a proposition how you'd want to break it and we could discuss it more, allowing people already using the crate to also participate?

Maybe would be even nicer to integrate crates such as failure to the mix.

from a2.

Thanks for the response and the open mind.

I will open a PR if I can convert my thought into a reasonable change.

PS:

Thanks for the example code of your consumer, it helps a lot.

from a2.