{"action":"opened","issue":{"url":"https://api.github.com/repos/timehop/apns/issues/50","labels_url":"https://api.github.com/repos/timehop/apns/issues/50/labels{/name}","comments_url":"https://api.github.com/repos/timehop/apns/issues/50/comments","events_url":"https://api.github.com/repos/timehop/apns/issues/50/events","html_url":"https://github.com/timehop/apns/issues/50","id":77181427,"number":50,"title":"Multiple Connection / High Throughput / Batching Ideas","user":{"login":"tylrtrmbl","id":1058478,"avatar_url":"https://avatars.githubusercontent.com/u/1058478?v=3","gravatar_id":"","url":"https://api.github.com/users/tylrtrmbl","html_url":"https://github.com/tylrtrmbl","followers_url":"https://api.github.com/users/tylrtrmbl/followers","following_url":"https://api.github.com/users/tylrtrmbl/following{/other_user}","gists_url":"https://api.github.com/users/tylrtrmbl/gists{/gist_id}","starred_url":"https://api.github.com/users/tylrtrmbl/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tylrtrmbl/subscriptions","organizations_url":"https://api.github.com/users/tylrtrmbl/orgs","repos_url":"https://api.github.com/users/tylrtrmbl/repos","events_url":"https://api.github.com/users/tylrtrmbl/events{/privacy}","received_events_url":"https://api.github.com/users/tylrtrmbl/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-05-17T01:44:20Z","updated_at":"2015-05-17T01:44:20Z","closed_at":null,"body":"It's clear that:\r\n\r\n- Reliable delivery (and its limitations) is not generally well understood by users of the library\r\n- Error handling / reporting should be more clearly exposed\r\n- Some clients will benefit from a Nagle's-like or `TCP_CORK`-like implementation of sending APNS messages\r\n\r\nIn my mind, these are all closely intertwined with throughput. Any of these can be solved very easily at the expense of throughput. With high throughput in mind, these become more challenging to address. :)\r\n\r\nThis issue is a teaser. I have some ideas, but I'm going to wait until we're finished nailing down #31 before opening that bucket of worms. That way we can avoid the API moving every which way at once.\r\n\r\nForgive me,\r\n\r\n@tylrtrmbl"}}