Libraries tagged by wait

Go to Download

This is a frame for laravel project.

Go to Download

To zip/unzip files/folders easily

Go to Download

waiterphp的核心类库

Go to Download

waiterphp builder

Go to Download

waiterphp应用开发框架

Go to Download

waiterphp后台类库

Go to Download

## 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

Ability to wait with sending notifications until a specific action completes

Go to Download

Managing php-cli processes from under php-cgi and waiting for a response from the last process. (Only for * nix systems with shared memory support).

Go to Download

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

Go to Download

Add responses to Laravel Jobs - allowing your application to wait for a response from a dispatched job.

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