Since you wrote that you employ Spring MCV I presume you don't use any page state when constructing your dynamic resource, instead you parse URL parameters. Thus your resource seems to be shared resource.
I used to extend WebResource (provide your own dynamic implementation of IResourceStream) for that task and register it as a shared resource at the application initialization time. For the resources that have persistent URLs I used to mount them with shared resource url coding strategy. Since shared resources are handled by Wicket filter I always have access to the session and can check permissions. I like that I can handle the cache by throwing AbortWithWebErrorCodeException(HttpServletResponse.SC_NOT_MODIFIED) exception if the resource hasn't changed since recent download. I would like to ask Igor to comment on that. Code maintainers expressed some thoughts about future support of IResourceStream. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/efficient-resource-downloading-tp2164866p2174267.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
