[jira] [Updated] (WICKET-5621) Store more information to/with BufferedWebResponse that survives multi-RequestCycle redirect

["Hendy Irawan (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-5621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hendy Irawan updated WICKET-5621:
---------------------------------

    Issue Type: Improvement  (was: Bug)

> Store more information to/with BufferedWebResponse that survives multi-RequestCycle redirect
> --------------------------------------------------------------------------------------------
>
>                 Key: WICKET-5621
>                 URL: https://issues.apache.org/jira/browse/WICKET-5621
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 6.16.0
>            Reporter: Hendy Irawan
>
> From [~mgrigorov] :
> It seems {{org.apache.wicket.response.filter.ServerAndClientTimeFilter}} and 
> the other similar filters lie because they use the current request cycle's 
> begin time. The processing time when there is a buffered 
> response should be quite small. 
> The reported time at the moment is not very useful. 
> It seems we need to store more information to/with BufferedWebResponse to 
> be able to cover the requirements in this mail thread and 
> WICKET-5129.
> Original thread and use case: http://apache-wicket.1842946.n4.nabble.com/How-to-get-PageClass-from-BufferedResponseRequestHandler-And-how-to-quot-link-quot-related-requests-td4666247.html



--
This message was sent by Atlassian JIRA
(v6.2#6252)