attach()
detach()
getEvent()
getEventManager()
sendResponse()
setEvent()
setEventManager()
attachDefaultListeners()
$event
$eventManager
$listeners
Abstract aggregate listener
attach(\Zend\EventManager\EventManagerInterface $events) : void
Implementors may add an optional $priority argument; the EventManager implementation will pass this to the aggregate.
detach(\Zend\EventManager\EventManagerInterface $events) : void
| inherited_from | \Zend\EventManager\AbstractListenerAggregate::detach() |
|---|
getEvent() : \Zend\Mvc\ResponseSender\SendResponseEvent
getEventManager() : \Zend\EventManager\EventManagerInterface
Lazy-loads an EventManager instance if none registered.
setEvent(\Zend\Mvc\ResponseSender\SendResponseEvent $e) : \Zend\Mvc\ResponseSender\SendResponseEvent
setEventManager(\Zend\EventManager\EventManagerInterface $eventManager) : \Zend\Mvc\SendResponseListener
attachDefaultListeners() : \Zend\Mvc\SendResponseListener
The order in which the response sender are listed here, is by their usage: PhpEnvironmentResponseSender has highest priority, because it's used most often. ConsoleResponseSender and SimpleStreamResponseSender are not used that often, yo they have a lower priority. You can attach your response sender before or after every default response sender implementation. All default response sender implementation have negative priority. You are able to attach listeners without giving a priority and your response sender would be first to try.
$listeners : \Zend\Stdlib\CallbackHandler[]
| inherited_from | \Zend\EventManager\AbstractListenerAggregate::$$listeners |
|---|