Libraries tagged by wait

## OpenAPI Endpoints OpenAPI Spec in JSON OpenAPI Spec in YAML ### Offboarding Every service conntected to Grünes Netz needs to remove users when they are removed from `saml.gruene.de`. Connected services need to pull a list of users waiting for removal at least once a week. api.gruene.de needs to be informed whether the user did not exist or was removed. API tokens can be obtained from `[email protected]`.

Go to Download

In-process channels, mutexes, wait groups, and stacks for coroutine-aware coordination for Switon Framework

Go to Download

Ability to wait with sending notifications until a specific action completes

Go to Download

Payment-agnostic event management for Laravel: events, tickets, applications, queue, waitlist, refunds, transfers, requirements, sponsors, announcements.

Go to Download

A professional practice on omnibase - the office, its team, its hours and contact (core), appointments by slot or by request (Booking), an encrypted document vault per recipient with its access log (Share), a video room with a waiting room, its calls carried by a glitchr/omnimeet gateway - from browser to browser by default (Visio). Shared by the regulated professions: health, notaries, lawyers.

Go to Download

Send a post request with parameters async and without wait for a response

Go to Download

Testcontainers module for MockServer — starts a mockserver/mockserver Docker container, waits for readiness, and exposes connection helpers plus a ready-wired MockServer client.

Go to Download

Event management extension with list and detail views and iCal export. Supports event registration with waiting list. Categories use TYPO3 `sys_category`.

Go to Download

LaravelConcurrentLimiter is a lightweight Laravel middleware that limits concurrent requests per user (or IP). It delays requests until a slot is available or returns an error after a maximum wait time, protecting your app from resource exhaustion and ensuring fair usage under high load.

Go to Download

Documentation of the Billbee REST API to connect a Billbee account to external aplications. ## Endpoint The Billbee API endpoint base url is https://api.billbee.io/api/v1 ## Activation You have to enable the API in the settings of your Billbee account. In addition you need a Billbee API Key identifying the application you develop. To get an API key, send a mail to [email protected] and send us a short note about what you are building. ## Authorization & security Because you can access private data with the Billbee API, every request has to be sent over https and must * Contain a valid API Key identifying the application/developer. It has to be sent as the HTTP header X-Billbee-Api-Key * Contain a valid user login with billbee username and api password in form of a basic auth HTTP header ## Throttling 50 calls per second for each API Key. 10 calls per second for each API Key in combination with Billbee user. Besides that each endpoint has a throttle of max 2 requests per second per combination of API Key and Billbee user. When you exceed the throttle threshold, the API will return a HTTP 429 status code and a Retry-After-Header indicating how many seconds you will have to wait before you can call the API again.

Go to Download

Wrapper for Forecast.io API that supports many simultaneous API calls, substantially reducing wait time for any applications needing to look up weather conditions en masse.

Go to Download

Validate APIPlatform filter values, waiting https://github.com/api-platform/core/pull/1723 to be merged

Go to Download

A small retry library with the possibility to wait before retrying.

Go to Download

The Laravel Framework. Removed WriterPDO for batch and Removed wait lock for update for batch transaction

Go to Download

A re-usable tchatbot PHP implementation to never be alone again. Hum, wait... What?

Go to Download