symfony/src/Symfony/Bundle/FrameworkBundle/Resources/config/profiling.xml

<?xml version="1.0" ?>

<container xmlns="http://symfony.com/schema/dic/services"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">

    <parameters>
        <parameter key="profiler.class">Symfony\Component\HttpKernel\Profiler\Profiler</parameter>
        <parameter key="profiler_listener.class">Symfony\Bundle\FrameworkBundle\Profiler\ProfilerListener</parameter>
    </parameters>

    <services>
        <service id="profiler" class="%profiler.class%" scope="request">
            <tag name="monolog.logger" channel="profiler" />
            <argument type="service" id="profiler.storage" />
            <argument type="service" id="logger" on-invalid="null" />
        </service>

        <service id="profiler.storage" class="" public="false">
            <argument /> <!-- DSN -->
            <argument /> <!-- Username -->
            <argument /> <!-- Password -->
            <argument /> <!-- Lifetime -->
        </service>

        <service id="profiler_listener" class="%profiler_listener.class%">
            <tag name="kernel.listener" event="onCoreResponse" />
            <tag name="kernel.listener" event="onCoreException" />
            <tag name="kernel.listener" event="onCoreRequest" />
            <argument type="service" id="service_container" />
            <argument type="service" id="profiler.request_matcher" on-invalid="null" />
            <argument /> <!-- Only exceptions? -->
            <argument /> <!-- Only master requests? -->
        </service>
    </services>
</container>
[ProfiledBundle] moved debug tools from WebBundle to ProfilerBundle 2010-03-01 11:47:28 +00:00			`<?xml version="1.0" ?>`

replaced symfony-project.org by symfony.com 2011-03-06 11:40:06 +00:00			`<container xmlns="http://symfony.com/schema/dic/services"`
[ProfiledBundle] moved debug tools from WebBundle to ProfilerBundle 2010-03-01 11:47:28 +00:00			`xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"`
replaced symfony-project.org by symfony.com 2011-03-06 11:40:06 +00:00			`xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">`
[ProfiledBundle] moved debug tools from WebBundle to ProfilerBundle 2010-03-01 11:47:28 +00:00
fixed coding standards for XML and YAML files 2010-06-11 09:06:44 +01:00			`<parameters>`
[FrameworkBundle] converted the special Profiler class to a DIC compiler class 2010-12-23 11:48:45 +00:00			`<parameter key="profiler.class">Symfony\Component\HttpKernel\Profiler\Profiler</parameter>`
fixed profiler when using ESI in dev env 2011-02-19 09:59:55 +00:00			`<parameter key="profiler_listener.class">Symfony\Bundle\FrameworkBundle\Profiler\ProfilerListener</parameter>`
fixed coding standards for XML and YAML files 2010-06-11 09:06:44 +01:00			`</parameters>`

			`<services>`
fixed profiler when using ESI in dev env 2011-02-19 09:59:55 +00:00			`<service id="profiler" class="%profiler.class%" scope="request">`
Added monolog tags to create all core channels 2011-02-25 22:09:45 +00:00			`<tag name="monolog.logger" channel="profiler" />`
[ProfilerBundle] refactored the profiler bundle 2010-06-16 09:38:41 +01:00			`<argument type="service" id="profiler.storage" />`
			`<argument type="service" id="logger" on-invalid="null" />`
			`</service>`

[FrameworkBundle] made the profiler easily configurable 2011-03-16 14:50:48 +00:00			`<service id="profiler.storage" class="" public="false">`
			`<argument /> <!-- DSN -->`
			`<argument /> <!-- Username -->`
			`<argument /> <!-- Password -->`
			`<argument /> <!-- Lifetime -->`
fixed coding standards for XML and YAML files 2010-06-11 09:06:44 +01:00			`</service>`

made all event listeners lazy loaded * The register() method on all listeners has been removed * Instead, the information is now put directly in the DIC tag For instance, a listener on core.request had this method: public function register(EventDispatcher $dispatcher, $priority = 0) { $dispatcher->connect('core.response', array($this, 'filter'), $priority); } And this tag in the DIC configuration: <tag name="kernel.listener" /> Now, it only has the following configuration: <tag name="kernel.listener" event="core.response" method="filter" priority="0" /> The event and method attributes are now mandatory. 2011-01-23 17:02:16 +00:00			`<service id="profiler_listener" class="%profiler_listener.class%">`
renamed filterCore* to onCore* The onCore* events are fired at some pre-defined points during the handling of a request. At this is more important than the fact that you can change things from the event. 2011-03-17 16:01:59 +00:00			`<tag name="kernel.listener" event="onCoreResponse" />`
Replaced EventDispatcher by Doctrine's EventManager implementation Doctrine's EventManager implementation has several advantages over the EventDispatcher implementation of Symfony2. Therefore I suggest that we use their implementation. Advantages: * Event Listeners are objects, not callbacks. These objects have handler methods that have the same name as the event. This helps a lot when reading the code and makes the code for adding an event listener shorter. * You can create Event Subscribers, which are event listeners with an additional getSubscribedEvents() method. The benefit here is that the code that registers the subscriber doesn't need to know about its implementation. * All events are defined in static Events classes, so users of IDEs benefit of code completion * The communication between the dispatching class of an event and all listeners is done through a subclass of EventArgs. This subclass can be tailored to the type of event. A constructor, setters and getters can be implemented that verify the validity of the data set into the object. See examples below. * Because each event type corresponds to an EventArgs implementation, developers of event listeners can look up the available EventArgs methods and benefit of code completion. * EventArgs::stopPropagation() is more flexible and (IMO) clearer to use than notifyUntil(). Also, it is a concept that is also used in other event implementations Before: class EventListener { public function handle(EventInterface $event, $data) { ... } } $dispatcher->connect('core.request', array($listener, 'handle')); $dispatcher->notify('core.request', new Event(...)); After (with listeners): final class Events { const onCoreRequest = 'onCoreRequest'; } class EventListener { public function onCoreRequest(RequestEventArgs $eventArgs) { ... } } $evm->addEventListener(Events::onCoreRequest, $listener); $evm->dispatchEvent(Events::onCoreRequest, new RequestEventArgs(...)); After (with subscribers): class EventSubscriber { public function onCoreRequest(RequestEventArgs $eventArgs) { ... } public function getSubscribedEvents() { return Events::onCoreRequest; } } $evm->addEventSubscriber($subscriber); $evm->dispatchEvent(Events::onCoreRequest, new RequestEventArgs(...)); 2011-03-05 14:30:34 +00:00			`<tag name="kernel.listener" event="onCoreException" />`
Merge remote branch 'symfony/master' into event-manager Conflicts: src/Symfony/Bundle/AsseticBundle/CacheWarmer/AssetWriterCacheWarmer.php src/Symfony/Bundle/AsseticBundle/Tests/CacheWarmer/AssetWriterCacheWarmerTest.php src/Symfony/Bundle/FrameworkBundle/Profiler/ProfilerListener.php src/Symfony/Bundle/FrameworkBundle/Resources/config/profiling.xml src/Symfony/Component/HttpKernel/HttpKernel.php src/Symfony/Component/Security/Http/Firewall/AbstractAuthenticationListener.php src/Symfony/Component/Security/Http/Firewall/AbstractPreAuthenticatedListener.php 2011-03-17 11:34:12 +00:00			`<tag name="kernel.listener" event="onCoreRequest" />`
fixed profiler when using ESI in dev env 2011-02-19 09:59:55 +00:00			`<argument type="service" id="service_container" />`
added a way to conditionnaly enable the profiler based on the request 2010-09-02 12:54:32 +01:00			`<argument type="service" id="profiler.request_matcher" on-invalid="null" />`
[FrameworkBundle] made the profiler easily configurable 2011-03-16 14:50:48 +00:00			`<argument /> <!-- Only exceptions? -->`
Add a configuration option to restrict profiler storage to the master request We a currently working on a project were a single requested URL typically leads to some hundred controller calls. Using the dev controller got incredibly slow since recent Symfony2 changes because for each controller invocation a new entry gets added to the profiler storage (totalling over 100mb of data on each request in our case). With the new configuration attribute "only-master-requests" it is possible to limit the profiler storage to the master requests, keeping the profiler usable for us. 2011-03-29 15:58:34 +01:00			`<argument /> <!-- Only master requests? -->`
fixed coding standards for XML and YAML files 2010-06-11 09:06:44 +01:00			`</service>`
			`</services>`
[ProfiledBundle] moved debug tools from WebBundle to ProfilerBundle 2010-03-01 11:47:28 +00:00			`</container>`