On Fri, Feb 18, 2011 at 10:09 PM, Lukas Kahwe Smith <[email protected]> wrote:
> so we need to identify the "outer" request. now the inner ESI tags are 
> defined via the render twig tag which generates the ESI url, which could 
> include an additional GET parameter to disable the toolbar. potentially we 
> could also use a cookie to pass the profiler "id" of the given subrequest to 
> the "outer" page. hopefully we could ensure somehow that the cookie doesnt 
> interfere with the reverse proxies work via some sort of filtering.

There can be hundreds of sub-requests for one given page. I don't
think you really want to see all of them in your toolbar. What would
be cool if it's not there yet though is to have a tab in the profiler
interface that is showing you all the subrequests executed, with url
and more info, that way you could jump to one of their profiler report
there.

Cheers

-- 
Jordi Boggiano
@seldaek :: http://seld.be/

-- 
If you want to report a vulnerability issue on symfony, please send it to 
security at symfony-project.com

You received this message because you are subscribed to the Google
Groups "symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en

Reply via email to