amazonka-sqs 1.3.5 → 1.3.6

raw patch · 3 files changed

+13/−11 lines, 3 filesdep ~amazonka-coredep ~amazonka-sqsdep ~amazonka-testPVP ok

version bump matches the API change (PVP)

Dependency ranges changed: amazonka-core, amazonka-sqs, amazonka-test

API changes (from Hackage documentation)

Files

• README.md +1/−1
• amazonka-sqs.cabal +5/−5
• gen/Network/AWS/SQS/ChangeMessageVisibility.hs +7/−5

@@ -8,7 +8,7 @@  ## Version -`1.3.5`+`1.3.6`   ## Description

@@ -1,5 +1,5 @@ name:                  amazonka-sqs-version:               1.3.5+version:               1.3.6 synopsis:              Amazon Simple Queue Service SDK. homepage:              https://github.com/brendanhay/amazonka bug-reports:           https://github.com/brendanhay/amazonka/issues@@ -94,7 +94,7 @@         , Network.AWS.SQS.Types.Sum      build-depends:-          amazonka-core == 1.3.5.*+          amazonka-core == 1.3.6.*         , base          >= 4.7     && < 5  test-suite amazonka-sqs-test@@ -114,9 +114,9 @@         , Test.AWS.SQS.Internal      build-depends:-          amazonka-core == 1.3.5.*-        , amazonka-test == 1.3.5.*-        , amazonka-sqs == 1.3.5.*+          amazonka-core == 1.3.6.*+        , amazonka-test == 1.3.6.*+        , amazonka-sqs == 1.3.6.*         , base         , bytestring         , lens

@@ -27,11 +27,13 @@ -- in the /Amazon SQS Developer Guide/.) -- -- For example, let\'s say you have a message and its default message--- visibility timeout is 30 minutes. You could call--- 'ChangeMessageVisiblity' with a value of two hours and the effective--- timeout would be two hours and 30 minutes. When that time comes near you--- could again extend the time out by calling ChangeMessageVisiblity, but--- this time the maximum allowed timeout would be 9 hours and 30 minutes.+-- visibility timeout is 5 minutes. After 3 minutes, you call+-- 'ChangeMessageVisiblity' with a timeout of 10 minutes. At that time, the+-- timeout for the message would be extended by 10 minutes beyond the time+-- of the ChangeMessageVisibility call. This results in a total visibility+-- timeout of 13 minutes. You can continue to call ChangeMessageVisibility+-- to extend the visibility timeout to a maximum of 12 hours. If you try to+-- extend beyond 12 hours, the request will be rejected. -- -- There is a 120,000 limit for the number of inflight messages per queue. -- Messages are inflight after they have been received from the queue by a