Zend Framework
LICENSE
This source file is subject to the new BSD license that is bundled with this package in the file LICENSE.txt. It is also available through the world-wide-web at this URL: http://framework.zend.com/license/new-bsd If you did not receive a copy of the license and are unable to obtain it through the world-wide-web, please send an email to license@zend.com so we can send you a copy immediately.
Implements communication via HTTP request and response headers for Wildfire Protocols.
integer $_controllerPluginStackIndex = '999'
The index of the plugin in the controller dispatch loop plugin stack
string $_headerPrefix = 'X-WF-'
The string to be used to prefix the headers.
Zend_Wildfire_Channel_HttpHeaders $_instance = 'null'
Singleton instance
array $_protocols = 'null'
The protocol instances for this channel
_initProtocol(
string $uri
)
:
object
Initialize a new protocol
_registerControllerPlugin(
)
:
void
Register this object as a controller plugin.
destroyInstance(
)
:
void
Destroys the singleton instance
Primarily used for testing.
dispatchLoopShutdown(
)
:
void
Flush messages to headers as late as possible but before headers have been sent.
flush(
)
:
boolean
Flush all data from all protocols and send all data to response headers.
getInstance(
$skipCreate $skipCreate
=
false
)
:
Zend_Wildfire_Channel_HttpHeaders
Get or create singleton instance
getProtocol(
string $uri
)
:
object
Get the instance of a give protocol for this channel
getRequest(
)
:
Zend_Controller_Request_Abstract
Get the request object
getResponse(
)
:
Zend_Controller_Response_Abstract
Get the response object
init(
string $class
=
null
)
:
Zend_Wildfire_Channel_HttpHeaders
Initialize singleton instance.
isReady(
boolean $forceCheckRequest
=
false
)
:
boolean
Determine if channel is ready.
The channel is ready as long as the request and response objects are initialized, can send headers and the FirePHP header exists in the User-Agent.
If the header does not exist in the User-Agent, no appropriate client is making this request and the messages should not be sent.
A timing issue arises when messages are logged before the request/response objects are initialized. In this case we do not yet know if the client will be able to accept the messages. If we consequently indicate that the channel is not ready, these messages will be dropped which is in most cases not the intended behaviour. The intent is to send them at the end of the request when the request/response objects will be available for sure.
If the request/response objects are not yet initialized we assume if messages are logged, the client will be able to receive them. As soon as the request/response objects are availoable and a message is logged this assumption is challenged. If the client cannot accept the messages any further messages are dropped and messages sent prior are kept but discarded when the channel is finally flushed at the end of the request.
When the channel is flushed the $forceCheckRequest option is used to force a check of the request/response objects. This is the last verification to ensure messages are only sent when the client can accept them.
setControllerPluginStackIndex(
integer $index
)
:
integer
Set the index of the plugin in the controller dispatch loop plugin stack