igorw / retry

A tiny library for retrying failing operations.

retry

A tiny library for retrying failing operations.

Since the network is reliable, things should always work. Am I right? For those cases when they don't, there is retry.

<?
use function igorw\retry;

// retry an operation up to 5 times
$user = retry(5, function () use ($id) {
    return User::find($id);
});

// here is why you want to start using HHVM
$user = retry(5, () ==> User::find($id));

// this is probably a bad idea
$user = retry(INF, () ==> {
    throw new RuntimeException('never gonna give you up');
});
?>

I know. You're welcome.

retry's Issues

Timeout idea.

This is more a question than an issue. Do you think an optional parameter for timeout will be beneficial?

If found this code in a legacy project I am mantaining

    /**
     * Keep trying a number of times until it actually saves. This is for really important tasks.
     *
     * @param $entity
     * @param int $iterations
     * @return bool
     */
    public function reallySave( $entity, $iterations = 5 ) {
        for( $i = 0; $i < $iterations; $i++ ) {
            if( $entity->save() ) {
                return TRUE;
            }

            //sleep for 100 milliseconds between each try. Without the delay two back to back attempts are likely to fail.
            usleep( 100 * 1000 );
        }
        return FALSE;
    }

I don't know if this is a bad practice, but I think retry could replace this.

add stable tag

Looks like everything is working great with retry, why not add a 0.1.0 or 1.0.0 tag?

Recursion instead of goto

May I ask if there is a reason why you prefer using goto instead of function recursion?

ltidchldkiilvhtjctuchul

How about a tag

So we can finally start using this in projects that have the default minimum stability (stable) specified in Composer.