PHP download

Download the PHP package aihimel/laravel-waiting-request without Composer

On this page you can find all versions of the php package aihimel/laravel-waiting-request. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

Table of contents
Download aihimel/laravel-waiting-request
More information about aihimel/laravel-waiting-request
Files in aihimel/laravel-waiting-request

Vendor aihimel
Package laravel-waiting-request
Short Description A simple implementation for holding request untill a job or background process is done.
License GPL-3.0-or-later

Keywords package php backend request laravel blocking waiting

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:

If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.

Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
To use Composer is sometimes complicated. Especially for beginners.
Composer needs much resources. Sometimes they are not available on a simple webspace.
If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.

Please rate this library. Is it a good library?

Example code of aihimel/laravel-waiting-request

Informations about the package laravel-waiting-request

Laravel Waiting Request

A simple implementation for holding requests until a job or background process is finished. This package allows you to conditionally block requests and wait for them to be unblocked within a specified timeout.

Installation

You can install the package via composer:

Configuration

You can publish the configuration file using:

The published configuration file config/waiting-request.php contains the following defaults:

Key	Env	Purpose
`cache_prefix`	`LW_REQUEST_CACHE_PREFIX`	Prepended to every cache key the package writes.
`timeout`	`LW_REQUEST_MAX_WAITING_TIME`	How long `whenResolved()` waits before giving up.
`check_interval`	`LW_REQUEST_CHECK_INTERVAL`	How often `whenResolved()` polls between checks.
`max_blocking_time`	`LW_REQUEST_MAX_BLOCKING_TIME`	Default lifetime of a blocker. After this many seconds, the next `isBlocked()` / `whenResolved()` call evicts the blocker and emits a warning log.

Usage

Basic Example

Suppose you have a resource that is being processed in the background (e.g., a large PDF generation or a data sync). You can block requests for this resource until the process is complete.

1. Add a Blocker

In your controller or job where the background process starts:

2. Wait for Resolution

In the request that needs to wait for the resource:

3. Resolve the Blocker

When the background process is finished:

Calling resolveBlocker() explicitly is still the recommended path — it releases the lock immediately so waiting requests can proceed and avoids the warning log emitted by the auto-expiry backstop (see below).

Checking if Blocked

You can also check if a resource is currently blocked without waiting:

Note: isBlocked() is not a pure read. If the blocker has passed its expiry, this call also forgets the cache entry and emits a Log::warning. Avoid placing it on a hot path that you expect to be side-effect-free.

Blocker Lifetime

Every blocker now has a finite lifetime.

The lifetime defaults to max_blocking_time from the config (10 seconds out of the box).
You can override it per call via the third argument to addBlocker().
When the lifetime is reached, the next isBlocked() (and therefore whenResolved()) call:
1. Deletes the cache entry, and
2. Emits Log::warning('Waiting-request blocker expired without being resolved', [...]) with class_path, resource_id, and expired_at in the context.

The log line goes through Laravel's Log facade, so it honors whatever channel and formatter your app has configured in config/logging.php.

If you have a background job that may take longer than 10 seconds, raise LW_REQUEST_MAX_BLOCKING_TIME (or pass an explicit TTL to addBlocker()) — otherwise the blocker will be auto-released while your job is still running, defeating the purpose of the lock.

Upgrading

From 1.x to 2.x

Version 2.x changes how blockers expire. The public method signatures stay backwards-compatible, but the runtime behavior changes:

Blockers now expire automatically. In 1.x, a blocker lived in cache until resolveBlocker() was called. In 2.x, every blocker has a finite lifetime (default 10s, configurable via LW_REQUEST_MAX_BLOCKING_TIME). If your job can exceed that, set the env or pass a per-call TTL.
isBlocked() has side effects. It deletes expired entries and emits a Log::warning.
The cache value shape changed from true to a Unix expiry timestamp. Any pre-upgrade blocker keys left in cache will be read as integer 1, treated as already-expired, deleted, and logged on first access. Flush the cache (or at least the keys under cache_prefix) when deploying the upgrade to avoid a one-time burst of warning logs and stale-blocker side effects.

See CHANGELOG.md for the full change list.

Features & Bug Fixes

If you find any bugs or have a feature request, please create an issue on GitHub.

Contributing

We welcome contributions! To become a contributor:

Fork the repository.
Clone your fork to your local machine.
Create a branch for your feature or bug fix.
Commit your changes with descriptive messages.
Push your branch to your fork.
Submit a Pull Request to the main repository.

Local Development

This package comes with a Docker-based development environment.

Build container

Run automated tests

Run PHPCS code inspection

Run PHPCBF auto-fixer

License

The GPL-3.0-or-later License. Please see License File for more information.

All versions of laravel-waiting-request with dependencies

PHP Build Version

Package Version

Version v2.0.0 Release 23. May 2026
create-project require 0 people chose require and
0 people chose create-project.

Download

Download latest version of laravel-waiting-request from vendor aihimel

Requires illuminate/support Version ^10.0 || ^11.0 || ^12.0 || ^13.0

Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package aihimel/laravel-waiting-request contains the following files

Loading the files please wait ...