[
https://issues.apache.org/jira/browse/WICKET-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17197207#comment-17197207
]
Emond Papegaaij commented on WICKET-6831:
-----------------------------------------
No, throwing an exception after flushing will not work, but IMHO throwing an
exception before flushing is not very nice to a user. It will trigger the
application server's 500 error page, most likely with a stacktrace. To be
honest, I'd prefer the logging and swallowing the exception, also for buffered
responses.
> Try to flush the response before detach
> ---------------------------------------
>
> Key: WICKET-6831
> URL: https://issues.apache.org/jira/browse/WICKET-6831
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-core
> Affects Versions: 9.0.0
> Reporter: Emond Papegaaij
> Priority: Major
>
> The current behavior makes the browser wait for cleanup on the server-end.
> The request is only flushed after detach and serialization of the pages. As
> the processing of the request has already completed, it is not needed to let
> the browser wait for the server to be cleaning up.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
