christeredvartsen

Simple retry strategy for Guzzle 7

APIs might implement rate limiting, and if they do your clients might experience 429 Too Many Requests responses with a Retry-After header, informing your client how long it should wait before making the next request. And being good internet citizens we should all implement support for this in our API clients.

Guzzle includes a retry middleware class that can be used to handle this.

The implementation in this gist is a PoC, so feel free to build upon it, and comment if you think something should be added / removed.

christeredvartsen

<?php
// Lookbehinds require fixed length, but lookaheads does not, so just reverse the string
$string = 'some string with _foo_ and _bar_ and http://example.com/some_foo_bar';
$replaced = strrev(preg_replace('#_([a-zæøå -]+)_(?![^ ]+//:ptth)#i', '>me/<\1>me<', strrev($string)));
echo $replaced; // some string with <em>foo</em> and <em>bar</em> and http://example.com/some_foo_bar

christeredvartsen

<?php
$path = '/some/dir';
$dir = new RecursiveDirectoryIterator($path);
$iterator = new RecursiveIteratorIterator($dir);

foreach ($iterator as $entry) {
    print($entry->getRealPath() . PHP_EOL);
}