apnotic 0.9.0 → 0.9.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 5cb5a06e46cf7b22e0c960e30007dcd7dcd2fe33
-  data.tar.gz: f97f34e8538fd271cb0a169780136575a85d49b5
+  metadata.gz: 96a81fa7043cdf525821559c6f17f25ac3ed68e5
+  data.tar.gz: ce96f01178be6446a377c432e75dc084ec09eaab
 SHA512:
-  metadata.gz: 3036c76078e4d49bc86f314237ef7c731497028f899e39285a99178f3f1357196eb55f9f3e680e5cd2070e08ce9234fe486449394c889ee1a040caec4edf5218
-  data.tar.gz: a396a147c7667c004e483895719a7b6ab8f89291c45d423636bf3568c40a9e2513506dbe3134149bdaab4016ae5c848b8be25113b7c5387666c5c1b4f017624e
+  metadata.gz: 2dfd67c994bc476f175425cae6c49c1588b594e874677c13b9ef559711d61dca6d4978aeda4c7c86830c04d70a2220ae568eae8d3f8fb07249b0e022800036e3
+  data.tar.gz: 150029805a257482683b5ce5338baf2e8e75bd24978530ed004e5f28c957d7038029ab9799fed3e1a32e8e558716f01c72285dd1e982d48554db0ede222d6fda

data/.travis.yml

@@ -3,6 +3,7 @@ rvm:
   - 2.1
   - 2.2
   - 2.3.0
+  - 2.3.1
 
 branches:
   only:

data/README.md

@@ -34,7 +34,7 @@ require 'apnotic'
 # create a persistent connection
 connection = Apnotic::Connection.new(cert_path: "apns_certificate.pem", cert_pass: "pass")
 
-# create a notification for a specific device token 
+# create a notification for a specific device token
 token = "6c267f26b173cd9595ae2f6702b1ab560371a60e7c8a9e27419bd0fa4a42e58f"
 
 notification       = Apnotic::Notification.new(token)
@@ -58,7 +58,7 @@ A practical usage of a Sidekiq / Rescue worker probably has to:
 
  * Use a pool of persistent connections.
  * Send a push notification.
- * Remove a device with an invalid token. 
+ * Remove a device with an invalid token.
 
 An example of a Sidekiq worker with such features follows. This presumes a Rails environment, and a model `Device`.
 
@@ -116,20 +116,20 @@ It is also possible to create a connection that points to the Apple Development
 Apnotic::Connection.development(options)
 ```
 
-> The concepts of PRODUCTION and DEVELOPMENT are different from what they used to be in previous specifications. Anything built directly from XCode and loaded on your phone will have the app generate DEVELOPMENT tokens, while everything else (TestFlight, Apple Store, HockeyApp, ...) will be considered as PRODUCTION environment. 
+> The concepts of PRODUCTION and DEVELOPMENT are different from what they used to be in previous specifications. Anything built directly from XCode and loaded on your phone will have the app generate DEVELOPMENT tokens, while everything else (TestFlight, Apple Store, HockeyApp, ...) will be considered as PRODUCTION environment.
 
 #### Methods
 
  * **uri** → **`URI`**
- 
+
  Returns the URI of the APNS endpoint.
 
  * **cert_path** → **`string`**
- 
+
  Returns the path to the certificate
- 
+
  * **push(notification, timeout=30)** → **`Apnotic::Response` or `nil`**
- 
+
  Sends a notification. Returns `nil` in case a timeout occurs.
 
 
@@ -200,21 +200,21 @@ The response to a call to `connection.push`.
 
 #### Methods
 
+ * **ok?** → **`boolean`**
+
+ Returns if the push was successful.
+
  * **headers** → **`hash`**
- 
+
  Returns a Hash containing the Headers of the response.
 
  * **status** → **`string`**
- 
+
  Returns the status code.
 
  * **body** → **`hash` or `string`**
- 
- Returns the body of the response in Hash format if a valid JSON was returned, otherwise just the RAW body.
 
- * **headers** → **`boolean`**
- 
- Returns if the push was successful.
+ Returns the body of the response in Hash format if a valid JSON was returned, otherwise just the RAW body.
 
 
 ## Getting Your APNs Certificate
@@ -223,8 +223,8 @@ The response to a call to `connection.push`.
 
 Once you have the certificate from Apple for your application, export your key and the apple certificate as p12 files. Here is a quick walkthrough on how to do this:
 
-1. Click the disclosure arrow next to your certificate in Keychain Access and select the certificate and the key. 
-2. Right click and choose `Export 2 items…`. 
+1. Click the disclosure arrow next to your certificate in Keychain Access and select the certificate and the key.
+2. Right click and choose `Export 2 items…`.
 3. Choose the p12 format from the drop down and name it `cert.p12`.
 
 Optionally, you may covert the p12 file to a pem file (this step is optional because Apnotic natively supports p12 files):

data/apnotic.gemspec

@@ -18,7 +18,7 @@ Gem::Specification.new do |spec|
   spec.executables   = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
   spec.require_paths = ["lib"]
 
-  spec.add_dependency "net-http2", "~> 0.9.2"
+  spec.add_dependency "net-http2", "~> 0.10.0"
   spec.add_dependency "connection_pool", "~> 2.0"
 
   spec.add_development_dependency "bundler", "~> 1.3"

data/lib/apnotic/version.rb

@@ -1,3 +1,3 @@
 module Apnotic
-  VERSION = "0.9.0"
+  VERSION = "0.9.1"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: apnotic
 version: !ruby/object:Gem::Version
-  version: 0.9.0
+  version: 0.9.1
 platform: ruby
 authors:
 - Roberto Ostinelli
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2016-05-01 00:00:00.000000000 Z
+date: 2016-05-08 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: net-http2
@@ -16,14 +16,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.9.2
+        version: 0.10.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.9.2
+        version: 0.10.0
 - !ruby/object:Gem::Dependency
   name: connection_pool
   requirement: !ruby/object:Gem::Requirement