Decorators Handlers and Middleware Handlers Middleware HandlerStack Creating a Handler Testing Guzzle Clients Mock Handler History Middleware Test Web Server Using the test server FAQ Does Guzzle require Requirements 1. PHP 5.5.0 2. To use the PHP stream handler, allow_url_fopen must be enabled in your system's php.ini. 3. To use the cURL handler, you must have a recent version of cURL >= 7.19.4 compiled wrapper to send HTTP requests if cURL is not installed. Alternatively, you can provide your own HTTP handler used to send requests. Keep in mind that cURL is still required for sending concurrent requests.

Decorators Handlers and Middleware Handlers Middleware HandlerStack Creating a Handler Testing Guzzle Clients Mock Handler History Middleware Test Web Server Using the test server FAQ Does Guzzle require Requirements 1. PHP 5.5.0 2. To use the PHP stream handler, allow_url_fopen must be enabled in your system's php.ini. 3. To use the cURL handler, you must have a recent version of cURL >= 7.19.4 compiled wrapper to send HTTP requests if cURL is not installed. Alternatively, you can provide your own HTTP handler used to send requests. Keep in mind that cURL is still required for sending concurrent requests.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 1.5.4 Creating a Handler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 1.6 Testing Guzzle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 1.6.1 Mock Handler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 1.6.2 History Requirements 1. PHP 5.5.0 2. To use the PHP stream handler, allow_url_fopen must be enabled in your system’s php.ini. 3. To use the cURL handler, you must have a recent version of cURL >= 7.19.4 compiled

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 1.5.4 Creating a Handler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 1.6 Testing Guzzle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 1.6.1 Mock Handler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 1.6.2 History Requirements 1. PHP 5.5.0 2. To use the PHP stream handler, allow_url_fopen must be enabled in your system’s php.ini. 3. To use the cURL handler, you must have a recent version of cURL >= 7.19.4 compiled

Decorators Handlers and Middleware Handlers Middleware HandlerStack Creating a Handler Testing Guzzle Clients Mock Handler History Middleware Test Web Server Using the test server FAQ Does Guzzle require Requirements 1. PHP 5.5.0 2. To use the PHP stream handler, allow_url_fopen must be enabled in your system's php.ini. 3. To use the cURL handler, you must have a recent version of cURL >= 7.19.4 compiled wrapper to send HTTP requests if cURL is not installed. Alternatively, you can provide your own HTTP handler used to send requests. Installation The recommended way to install Guzzle is with Composer [http://getcomposer

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 1.5.4 Creating a Handler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 1.6 Testing Guzzle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 1.6.1 Mock Handler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 1.6.2 History Requirements 1. PHP 5.5.0 2. To use the PHP stream handler, allow_url_fopen must be enabled in your system’s php.ini. 3. To use the cURL handler, you must have a recent version of cURL >= 7.19.4 compiled

expression and a handler class. Order matters; the first matching rule is used. If the regular expression contains capturing groups, these groups are the path arguments and will be passed to the handler’s HTTP method subclasses of RequestHandler. The main entry point for a handler subclass is a method named after the HTTP method being handled: get(), post(), etc. Each handler may define one or more of these methods to handle with arguments corresponding to the capturing groups of the routing rule that matched. Within a handler, call methods such as RequestHandler.render or RequestHandler.write to produce a response. render()

just need to move the work, we need to prevent blocking on our event-handling threads. void event_handler(){ auto handle=spawn_background_task(); handle.wait(); // no benefit }Aside: Non-Blocking vs Lock-free event handler Pass data to a dedicated background threadHow do we move work off the current thread? Possible ways to move the work off the current thread: Spawn a new thread for each event handler Pass thread? Possible ways to move the work off the current thread: Spawn a new thread for each event handler Pass data to a dedicated background thread Submit tasks to a generic thread pool Submit tasks to

std::vector dA{ … }, dB{ … }, dO{ … }; try { sycl::queue gpuQueue{sycl::gpu_selector_v, async_handler{}}; sycl::buffer bufA{dA.data(), sycl::range{dA.size()}}; sycl::buffer bufB{dB.data() size()}}; sycl::buffer bufO{dO.data(), sycl::range{dO.size()}}; gpuQueue.submit([&](sycl::handler &cgh){ sycl::accessor inA(bufA, cgh, sycl::read_only); sycl::accessor inB(bufB, cgh std::vector dA{ … }, dB{ … }, dO{ … }; try { sycl::queue gpuQueue{sycl::gpu_selector_v, async_handler{}}; sycl::buffer bufA{dA.data(), sycl::range{dA.size()}}; sycl::buffer bufB{dB.data()

expression and a handler class. Order matters; the first matching rule is used. If the regular expression contains capturing groups, these groups are the path arguments and will be passed to the handler’s HTTP method subclasses of RequestHandler. The main entry point for a handler subclass is a method named after the HTTP method being handled: get(), post(), etc. Each handler may define one or more of these methods to handle called with arguments corresponding to the capturing groups of the routing rule that matched.Within a handler, call methods such as RequestHandler.render or RequestHandler.write to produce a response. render()