modConnectorResponseEncapsulates an HTTP response from the MODx manager.
Includes functions to manipluate header data, such as status codes, as well as manipulating the response body.
Located in /model/modx/modconnectorresponse.class.php (line 16)
modResponse | --modConnectorResponse
string
$_directory
(line 23)
The base location of the processors called by the connectors.
Inherited from modResponse
modResponse::$body
modResponse::$header
modResponse::$modx
Constructor __construct (line 30)
Creates a modConnectorResponse object.
outputArray (line 128)
Return arrays of objects (with count) converted to JSON.
Creates a modConnectorResponse object.
The JSON result includes two main elements, total and results. This format is used for list results.
outputContent (line 41)
Overrides modResponse::outputContent to provide connector-specific processing.
Creates a modConnectorResponse object.
setDirectory (line 142)
Set the physical location of the processor directory for the response handler.
Creates a modConnectorResponse object.
This allows for dynamic processor locations.
toJSON (line 160)
Converts PHP to JSON with JavaScript literals left in-tact.
Creates a modConnectorResponse object.
JSON does not allow JavaScript literals, but this function encodes certain identifiable literals and decodes them back into literals after modX::toJSON() formats the data.
_decodeLiterals (line 193)
Decodes strings encoded by _encodeLiterals to restore JavaScript literals.
Creates a modConnectorResponse object.
_encodeLiterals (line 174)
Encodes certain JavaScript literal strings for later decoding.
Creates a modConnectorResponse object.
Inherited From modResponse
modResponse::__construct()
modResponse::checkPreview()
modResponse::outputContent()
modResponse::sendRedirect()
Documentation generated on Fri, 17 Jun 2011 10:03:30 -0600 by phpDocumentor 1.4.3