[
https://issues.apache.org/jira/browse/WICKET-6286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15802624#comment-15802624
]
Jeremy commented on WICKET-6286:
--------------------------------
This solution seems overtly complex, given you can achieve the same thing with
resources.
Requiring a behaviour to be attached seems a bit too much, as well as the
potential page lock.
I'm also sure that's going to cause two requests.
Going from the click, to the server for the ajax behaviour, to the client with
some javascript, and then it requests the resource.
On top of that, it's an iframe.
I remember Firefox having a bunch of issues with iframe caching, and no amount
of anti-cache parameters would fix it.
> Would be good to have AjaxDownload available out of the box
> ------------------------------------------------------------
>
> Key: WICKET-6286
> URL: https://issues.apache.org/jira/browse/WICKET-6286
> Project: Wicket
> Issue Type: New Feature
> Components: wicket-extensions
> Affects Versions: 8.0.0-M2, 7.5.0
> Reporter: Maxim Solodovnik
> Assignee: Sven Meier
> Labels: patch
>
> Currently every project need to create own AjaxDownload component based on
> the Wiki example.
> Unfortunately this component has some issues with WebSockets
> Discussion: http://markmail.org/message/gizsnqh2qgypcgri
> PRs:
> https://github.com/apache/wicket/pull/190
> https://github.com/apache/wicket/pull/191
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
