Attach the aggregate to the specified event manager

attach(\Zend\EventManager\EventManagerInterface $events) : void

Implementors may add an optional $priority argument; the EventManager implementation will pass this to the aggregate.


Detach aggregate listeners from the specified event manager

detach(\Zend\EventManager\EventManagerInterface $events) : void

Retrieve the event manager

getEventManager() : \Zend\EventManager\EventManagerInterface

Lazy-loads an EventManager instance if none registered.


Send the response

sendResponse(\Zend\Mvc\MvcEvent $e) : void


Set the send response event

setEvent(\Zend\Mvc\ResponseSender\SendResponseEvent $e) : \Zend\Mvc\ResponseSender\SendResponseEvent

Inject an EventManager instance

setEventManager(\Zend\EventManager\EventManagerInterface $eventManager) : \Zend\Mvc\SendResponseListener

Register the default event listeners

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.





$eventManager : \Zend\EventManager\EventManagerInterface



$listeners : \Zend\Stdlib\CallbackHandler[]