Lines Matching refs:a
8 Due to the fact that these messages are immutable, this prompted a refactoring
9 of Guzzle to use a middleware based system rather than an event system. Any
13 functions that wrap handlers (or are injected into a
24 `guzzlehttp/promises` library. We use a custom promise library for three
28 promises are not recursive as they use a sort of trampolining technique.
31 2. Guzzle needs to have the ability to synchronously block on a promise to
32 wait for a result. Guzzle promises allows this functionality (and does
34 3. Because we need to be able to wait on a result, doing so using React
38 - `GuzzleHttp\Mimetypes` has been moved to a function in
44 option uses PHP's `http_build_query` to convert an array to a string. If you
45 need a different serialization technique, you will need to pass the query
46 string in as a string. There are a couple helper functions that will make
49 - Guzzle no longer has a dependency on RingPHP. Due to the use of a middleware
54 complexity in Guzzle, removes a dependency, and improves performance. RingPHP
55 will be maintained for Guzzle 5 support, but will no longer be a part of
57 - As Guzzle now uses a middleware based systems the event system and RingPHP
81 functions under the `GuzzleHttp` namespace. This requires either a Composer
97 workflow to become more about either returning a value (e.g., functional
98 middlewares) or setting a value on an object. Guzzle v6 has chosen the
102 you now create a stack based middleware function that intercepts a request on
103 the way in and the promise of the response on the way out. This is a much
124 to setup a handler middleware stack up front and inject the handler into a
129 // Create a handler stack that has all of the default middlewares attached
133 // Notice that we have to return a request object
147 option is now used to send a multipart/form-data POST request.
150 POST files to a multipart/form-data request.
163 HTTP requests. The `adapter` option in a `GuzzleHttp\Client` constructor
165 passing a `GuzzleHttp\Adapter\AdapterInterface`, you must now pass a PHP
191 `GuzzleHttp\get()`, `GuzzleHttp\post()`, etc.). Use a `GuzzleHttp\Client`
192 object as a replacement.
197 events. This control mechanism was used to stop a transfer of concurrent
199 by cancelling a pool of requests or each outstanding future request
205 body a response once the headers of the response were known. You can implement
206 a similar behavior in a number of ways. One example might be to use a
215 `GuzzleHttp\Message\MessageInterface::getHeader`. If you want to get a header
245 has been implemented yet, but hoping to utilize a PSR cache interface).
257 - `getAll` has been removed. Use `toArray` to convert a collection to an array.
276 - `AbstractHasDispatcher` has moved to a trait, `HasEmitterTrait`, and
278 event emitter of a request, client, etc. now uses the `getEmitter` method
283 - Use the `once()` method to add a listener that automatically removes itself
285 - Use the `listeners()` method to retrieve a list of event listeners rather than
301 Use the `on()` method to add a listener rather than the `addListener()` method.
318 - Sending requests in parallel is still possible, but batching is no longer a
333 return a request, but rather creates a request, sends the request, and returns
353 - `setUserAgent()` has been removed. Use a default request option instead. You
361 - The constructor now accepts only an associative array. You can include a
362 `base_url` string or array to use a URI template as the base URL of a client.
363 You can also specify a `defaults` key that is an associative array of default
364 request options. You can pass an `adapter` to use a custom adapter,
365 `batch_adapter` to use a custom adapter for sending requests in parallel, or
366 a `message_factory` to change the factory used to create HTTP requests and
368 - The client no longer emits a `client.create_request` event.
369 - Creating requests with a client no longer automatically utilize a URI
370 template. You must pass an array into a creational method (e.g.,
371 `createRequest`, `get`, `put`, etc.) in order to expand a URI template.
375 Messages no longer have references to their counterparts (i.e., a request no
376 longer has a reference to it's response, and a response no loger has a
377 reference to its request). This association is now managed through a
380 lifecycle of a request.
382 #### Requests with a body
386 separation between requests that contain a body and requests that do not
387 contain a body has been removed, and now `GuzzleHttp\Message\RequestInterface`
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
399 a `GuzzleHttp\Post\PostBody` body if the body was passed as an array or if
411 represented by an array of values or as a string. Header values are returned
412 as a string by default when retrieving a header value from a message. You can
413 pass an optional argument of `true` to retrieve a header value as an array
414 of strings instead of a single concatenated string.
437 system to work with request and response objects as a transaction.
445 Streaming requests can now be created by a client directly, returning a
446 `GuzzleHttp\Message\ResponseInterface` object that contains a body stream
465 The `configureRedirects()` method has been removed in favor of a
469 // Standard redirects with a default of a max of 5 redirects
472 // Strict redirects with a custom number of redirects
483 `GuzzleHttp\Stream\StreamInterface`. Creating a new body for a request no
496 Requests previously submitted a large number of requests. The number of events
497 emitted over the lifecycle of a request has been significantly reduced to make
498 it easier to understand how to extend the behavior of a request. All events
499 emitted during the lifecycle of a request now emit a custom
501 methods and a way in which to modify the transaction at that specific point in
502 time (e.g., intercept the request and set a response on the transaction).
504 - `request.before_send` has been renamed to `before` and now emits a
506 - `request.complete` has been renamed to `complete` and now emits a
510 - `error` is now an event that emits a `GuzzleHttp\Event\ErrorEvent`.
513 - `curl.callback.progress` has been removed. Use a custom `StreamInterface` to
514 maintain a status update.
515 - `curl.callback.write` has been removed. Use a custom `StreamInterface` to
517 - `curl.callback.read` has been removed. Use a custom `StreamInterface` to
520 `headers` is a new event that is emitted after the response headers of a
522 event emits a `GuzzleHttp\Event\HeadersEvent`.
524 You can intercept a request and inject a response using the `intercept()` event
525 of a `GuzzleHttp\Event\BeforeEvent`, `GuzzleHttp\Event\CompleteEvent`, and
532 The `Guzzle\Inflection` namespace has been removed. This is not a core concern
540 `Guzzle\Iterator\MethodProxyIterator` are nice, but not a core requirement of
545 it's easier to just wrap an iterator in a generator that maps values.
547 For a replacement of these iterators, see https://github.com/nikic/iter
568 Guzzle as a library to add this level of complexity to parsing messages.
584 - `GuzzleHttp\Subscriber\HttpError`: Throws errors when a bad HTTP response is
587 - `GuzzleHttp\Subscriber\Prepare`: Prepares the body of a request just before
621 - http://github.com/guzzle/command Provides a high level abstraction over web
629 Stream have moved to a separate package available at
632 `Guzzle\Stream\StreamInterface` has been given a large update to cleanly take
646 - `rewind` has been removed. Use `seek(0)` for a similar behavior.
653 - `readLine` has moved from an instance method to a static class method of
667 (instead of getting back a Response, you got a StreamInterface). Streaming
689 …leMagicMethods()` as deprecated. Magic methods can no longer be disabled on a Guzzle\Service\Clien…
696 3.7 introduces `request.options` as a parameter for a client configuration and as an optional argum…
697 request methods. When paired with a client's configuration settings, these options allow you to spe…
698 for various aspects of a request. Because these options make other previous configuration options r…
699 configuration options and methods of a client and AbstractCommand have been deprecated.
729 …tp\ClientInterface::get($uri = null, $headers = null, $options = array())`. You can still pass in a
731 … `Guzzle\Common\Collection::__construct($data)` to no longer accepts a null value for `$data` but a
747 - Removed `Guzzle\Http\ClientInterface::getCurlMulti()`. This is a very specific implementation det…
754 …ProviderInterface and DefaultCacheKeyProvider are no longer used. All of this logic is handled in a
755 CacheStorageInterface. These two objects and interface will be removed in a future version.
757 - Default cache TTLs are now handled by the CacheStorageInterface of a CachePlugin
771 * Mixed casing of headers are now forced to be a single consistent casing across all values for tha…
772 * Messages internally use a HeaderCollection object to delegate handling case-insensitive header re…
774 …For example, setHeader() first removes the header using unset on a HeaderCollection and then calls…
776 …ader implementations can be created for complex headers. When a message creates a header, it uses a
777 …HeaderFactory which can map specific headers to specific header classes. There is now a Link heade…
779 * Moved getLinks() from Response to just be used on a Link header object.
790 … optional $asString parameter from MessageInterface::getHeader(). Just cast the header to a string.
809 * All response header helper functions return a string rather than mixing Header objects and string…
812 * Removed the injecting of a request object onto a response object. The methods to get and set a re…
813 but are a no-op until removed.
814 * Most classes that used to require a `Guzzle\Service\Command\CommandInterface` typehint now reques…
816 …p\Message\RequestInterface::startResponse()` to the RequestInterface to handle injecting a response
817 on a request while the request is still being transferred
823 Base URLs of a client now follow the rules of http://tools.ietf.org/html/rfc3986#section-5.2.2 when…
842 Emitting IO events from a RequestMediator is now a parameter that must be set in a request's curl o…
843 'emit_io' key. This was previously set under a request's parameters using 'curl.emit_io'
851 to a single client can pollute requests dispatched from other clients.
853 If you still wish to reuse the same CurlMulti object with each client, then you can add a listener …
854 ServiceBuilder's `service_builder.create_client` event to inject a custom CurlMulti object into eac…
868 URLs no longer have a default path value of '/' if no path was specified.
894 …ed query parameters are no longer aggregated using a callback function. `Guzzle\Http\Query` now ha…
895 setAggregator() method that accepts a `Guzzle\Http\QueryAggregator\QueryAggregatorInterface` object…
896 responsible for handling the aggregation of multi-valued query string variables into a flattened ha…
967 <doc>Get a list of groups</doc>
970 <doc>Uses a search query to get a list of groups</doc>
974 <doc>Create a group</doc>
979 <doc>Delete a group by ID</doc>
986 <doc>Update a group</doc>
1006 "summary": "Get a list of groups"
1011 "summary": "Uses a search query to get a list of groups",
1024 "summary": "Create a group",
1043 "summary": "Delete a group",
1056 "summary": "Get a ticket",
1069 "summary": "Update a group",
1157 // $format is a string indicating desired message format -- @see MessageFormatter
1203 See issue #217 for a workaround, or use a version containing the fix.