Bump to v1.1.1

History.txt

@@ -1,3 +1,8 @@
+v1.1.1
+------
+
+  * Support retries in Replay mode
+
 v1.1.0
 ------
 

README.md

@@ -84,7 +84,7 @@ It's up to the developer's responsibility to complete message processing as soon
 possible. After 10 seconds (by default), the stop will be forced and a few messages
 already received but not processed yet may be lost.
 
-The ```:stop_timeout``` may be fine-tune when passing options to the tracker.
+The ```:stop_timeout``` may be fine-tuned when passing options to the tracker.
 
 ## Disconnections and Retries
 
@@ -93,6 +93,9 @@ backoff retry mechanism when a disconnection happens. The reconnections can be
 fine-tuned through the ```:max_retries``` and ```:backoff``` options passed to
 the ```track``` call.
 
+Note that the retries counter is reset each time the client manages to receive
+a message after a disconnection except in Replay mode (see further).
+
 ## Backfill
 
 Backfill is a feature provided by GNIP to avoid losing activities when being
@@ -112,9 +115,14 @@ object.
 Once Replay is activated, you use the stream as previously, starting by
 configuring some rules that define which activities you will recover. Once done,
 you can track the stream by specifying a timeframe with the ```:from```
-and ```:to options```. By default, replay happens over 30 minutes, starting 1
+and ```:to``` options. By default, replay happens over 30 minutes, starting 1
 hour ago.
 
+Regarding Replay mode and ```:max_retries```, the client does not reset the
+retry counter and will never reconnect more than the max number of retries
+specified. This specific retry behavior in Replay mode prevents the client from
+replaying the same timeframe again and again when GNIP is unstable.
+
 ## Errors
 
 All the errors that come from PowerTrack are defined through an ad-hoc exception

lib/powertrack/version.rb

@@ -1,3 +1,3 @@
 module PowerTrack
-  VERSION = '1.1.0'
+  VERSION = '1.1.1'
 end