Lines Matching refs:that

8 Due to the fact that these messages are immutable, this prompted a refactoring
13 functions that wrap handlers (or are injected into a
46   string in as a string. There are a couple helper functions that will make
51   more complexity than the benefits it provides. All HTTP handlers that were
59   it is possible to add your own type of event system that is powered by the
94 due to the fact that PSR-7 messages are immutable. Guzzle 5 relied on an event
102 you now create a stack based middleware function that intercepts a request on
129 // Create a handler stack that has all of the default middlewares attached
133     // Notice that we have to return a request object
166 `callable` that follows the RingPHP specification.
181 Removed "functions.php", so that Guzzle is truly PSR-4 compliant. The following
207 FnStream that has access to the transaction being sent. For example, when the
209 expectations, and if so, change the actual stream body that is being
227 - Guzzle no longer wraps every exception it throws. Only exceptions that are
283 - Use the `once()` method to add a listener that automatically removes itself
315 - Added the concept of adapters that are used to transfer requests over the
323 - QueryAggregators have been rewritten so that they are simply callable
363   You can also specify a `defaults` key that is an associative array of default
379 these transaction objects using request events that are emitted over the
386   separation between requests that contain a body and requests that do not
389 - Any method that previously accepts a `GuzzleHttp\Response` object now accept a
397   to control the format of a POST body. Requests that are created using a
421   been updated to properly handle headers that contain parameters (like the
446 `GuzzleHttp\Message\ResponseInterface` object that contains a body stream
481 `GuzzleHttp\Stream`. All classes and interfaces that once required
500 `GuzzleHttp\Event\EventInterface` object that contains context providing
501 methods and a way in which to modify the transaction at that specific point in
510 - `error` is now an event that emits a `GuzzleHttp\Event\ErrorEvent`.
520 `headers` is a new event that is emitted after the response headers of a
545   it's easier to just wrap an iterator in a generator that maps values.
597   functionality should instead be implemented with event listeners that occur
624   guzzle/command that provides request serialization and response parsing using
634 `Guzzle\Http\EntityBodyInterface` now that they have been removed. The number
645   using streams that implement `GuzzleHttp\Stream\MetadataStreamInterface`.
659 that contain additional metadata accessible via `getMetadata()`.
737 that implement them, but you should update your code to use alternative methods:
771 …asing of headers are now forced to be a single consistent casing across all values for that header.
810 * Removed cURL blacklist support. This is no longer necessary now that Expect, Accept, etc. are man…
814 * Most classes that used to require a `Guzzle\Service\Command\CommandInterface` typehint now reques…
842 Emitting IO events from a RequestMediator is now a parameter that must be set in a request's curl o…
895 setAggregator() method that accepts a `Guzzle\Http\QueryAggregator\QueryAggregatorInterface` object…