You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Xhelas <xh...@yahoo.fr> on 2009/04/20 01:38:08 UTC
Re: Good practice for temporary resource reference
Well, nobody has the same probelm as me? Is that a stupid question?
Xhelas wrote:
>
> I am doing an application with a lot of dynamical image creation. These
> images need to be cached client side, but their life time is bounded by
> the suer session's lifetime. So I create a lot of image resource
> references which url is used but the client. What I did not get in the APi
> is the way do "forget" those references, to unbind them to the
> application.
> Is there a canonical way to do so?
>
> Thanks for your reading.
>
> Alexandre
>
--
View this message in context: http://www.nabble.com/Good-practice-for-temporary-resource-reference-tp22773495p23128552.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Good practice for temporary resource reference
Posted by Xhelas <xh...@yahoo.fr>.
Yes it could. I figured out to override newSessionStore in the application to
have control over the undbind session call. I would have then remove the
request references registred in the session during its life time at this
time. I beleive that I have to remove my ResourceReference from the
SharedResources of the application.
I don't know if it it the correct way to do this. I found it by browsing the
wicket source code (thanks it is open source).
Anyone has tried to do something like that?
Regards
Alexandre
Scott Swank wrote:
>
> Does it make sense to just store them in the Wicket Session?
>
> Scott
>
>
> On Sun, Apr 19, 2009 at 4:38 PM, Xhelas <xh...@yahoo.fr> wrote:
>>
>> Well, nobody has the same probelm as me? Is that a stupid question?
>>
>>
>> Xhelas wrote:
>>>
>>> I am doing an application with a lot of dynamical image creation. These
>>> images need to be cached client side, but their life time is bounded by
>>> the suer session's lifetime. So I create a lot of image resource
>>> references which url is used but the client. What I did not get in the
>>> APi
>>> is the way do "forget" those references, to unbind them to the
>>> application.
>>> Is there a canonical way to do so?
>>>
>>> Thanks for your reading.
>>>
>>> Alexandre
>>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Good-practice-for-temporary-resource-reference-tp22773495p23128552.html
>> Sent from the Wicket - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Good-practice-for-temporary-resource-reference-tp22773495p23129153.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Good practice for temporary resource reference
Posted by Scott Swank <sc...@gmail.com>.
Does it make sense to just store them in the Wicket Session?
Scott
On Sun, Apr 19, 2009 at 4:38 PM, Xhelas <xh...@yahoo.fr> wrote:
>
> Well, nobody has the same probelm as me? Is that a stupid question?
>
>
> Xhelas wrote:
>>
>> I am doing an application with a lot of dynamical image creation. These
>> images need to be cached client side, but their life time is bounded by
>> the suer session's lifetime. So I create a lot of image resource
>> references which url is used but the client. What I did not get in the APi
>> is the way do "forget" those references, to unbind them to the
>> application.
>> Is there a canonical way to do so?
>>
>> Thanks for your reading.
>>
>> Alexandre
>>
>
> --
> View this message in context: http://www.nabble.com/Good-practice-for-temporary-resource-reference-tp22773495p23128552.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org