[
https://issues.apache.org/jira/browse/WICKET-6286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15809548#comment-15809548
]
Jeremy commented on WICKET-6286:
--------------------------------
The main point of the last comment was "but add some utility methods for adding
it to the page".
Because I don't think having it use a iframe by default is the best solution.
People who use a WebSocket, know they use a WebSocket, and they're the edge
case, not the other way around.
It might change, of course, but at that point, either a) The FileAPI would be
done, and we can just start a download directly, or b) We can just change the
default later on.
It might be wise to leave a note about this edge case: "Yeah, if you use a
WebSocket, you might have to output an iframe to initiate the download".
> 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)
