On Tue, May 11, 2010 at 11:24 AM, Zilvinas Vilutis <cika...@gmail.com> wrote:
> If you need to have the current session in a servlet, you may use the
> WicketSessionFilter which "injects" the wicket session into a
> ServletRequest.

rather it binds it to the threadlocal so you can say Session.get()

-igor

>
> In any way you want to use it - your chosen implementation of security part
> will still be heavyweight.
>
> Not sure if you can submit authentification details using a post request -
> but I'd suggest to use some simple web server as "lighthttpd" or "thttpd"
> for frequent resource access secured lighter then spring.
>
> Žilvinas Vilutis
>
> Mobile:   (+370) 652 38353
> E-mail:   cika...@gmail.com
>
>
> On Tue, May 11, 2010 at 11:06 AM, vladimir.kovalyuk <koval...@gmail.com>wrote:
>
>>
>> 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
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to