|
| 1 | +# Zend\Http |
| 2 | + |
| 3 | +## Overview |
| 4 | + |
| 5 | +`Zend\Http` is a primary foundational component of Zend Framework. Since much of |
| 6 | +what PHP does is web-based, specifically HTTP, it makes sense to have a |
| 7 | +performant, extensible, concise and consistent API to do all things HTTP. In |
| 8 | +nutshell, there are several parts of `Zend\Http`: |
| 9 | + |
| 10 | +* Context-less `Request` and `Response` classes that expose a fluent API for |
| 11 | +introspecting several aspects of HTTP messages: |
| 12 | + * Request line information and response status information |
| 13 | + * Parameters, such as those found in POST and GET |
| 14 | + * Message Body |
| 15 | + * Headers |
| 16 | +* A Client implementation with various adapters that allow for sending requests |
| 17 | +and introspecting responses. |
| 18 | + |
| 19 | +## Zend\Http Request, Response and Headers |
| 20 | + |
| 21 | +The Request, Response and Headers portion of the `Zend\Http` component provides |
| 22 | +a fluent, object-oriented interface for introspecting information from all the |
| 23 | +various parts of an HTTP request or HTTP response. The two main objects are |
| 24 | +`Zend\Http\Request` and `Zend\Http\Response`. These two classes are |
| 25 | +“context-less”, meaning that they model a request or response in the same way |
| 26 | +whether it is presented by a client (to **send** a request and **receive** a |
| 27 | +response) or by a server (to **receive** a request and **send** a response). In |
| 28 | +other words, regardless of the context, the API remains the same for |
| 29 | +introspecting their various respective parts. Each attempts to fully model a |
| 30 | +request or response so that a developer can create these objects from a factory, |
| 31 | +or create and populate them manually. |
0 commit comments