Interface ServerResponseContract
Contract interfaces enforce expected behavior in a non-colliding way. They are tasked with enforcing methods, and extending interfaces provided by standards and other packages for compatibility.
All valid oroboros classes MUST extend at
least one Contract Interface to be considered valid.
- oroboros\core\interfaces\contract\libraries\response\ServerResponseContract implements oroboros\core\interfaces\contract\libraries\response\ResponseContract
Namespace: oroboros\core\interfaces\contract\libraries\response
Package: oroboros\core\response
Category: contract-interfaces
License: The MIT License (MIT)
Author: Brian Dayhoff mopsyd@me.com
Version: 0.2.4-alpha
Since: 0.2.4-alpha
Link: bitbucket.org/oroborosframework/oroboros-core/wiki/development/api/contract_interface.md
Located at core/interfaces/contract/libraries/response/ServerResponseContract.php
Package: oroboros\core\response
Category: contract-interfaces
License: The MIT License (MIT)
Author: Brian Dayhoff mopsyd@me.com
Version: 0.2.4-alpha
Since: 0.2.4-alpha
Link: bitbucket.org/oroborosframework/oroboros-core/wiki/development/api/contract_interface.md
Located at core/interfaces/contract/libraries/response/ServerResponseContract.php
Methods summary
Methods inherited from oroboros\core\interfaces\contract\libraries\response\ResponseContract
__construct(),
getReasonPhrase(),
getStatusCode(),
withStatus()
Methods inherited from oroboros\core\interfaces\contract\libraries\stream\StreamContract
__destruct(),
__toString(),
close(),
detach(),
eof(),
getContents(),
getMetadata(),
getSize(),
isReadable(),
isSeekable(),
isWritable(),
read(),
rewind(),
seek(),
tell(),
write()