If it's called so many time per request that you are concerned about
performance why not associate the frequently used user details with
the session.

If numerous components are using the same model you could look to
refactor so that they use the same instance.

Ed.

On Thu, Nov 19, 2009 at 5:50 PM, Douglas Ferguson
<[email protected]> wrote:
> I am maintaining an app that is written in wicket.
>
> When a user logs in the userId is stored on the session.
> There is a method on the session object that returns a 
> UserAccountLoadableDetachable.
> This loadable detachable is created every time the method is called.
>
> My thought was that I could share it across the request.
>
> D/
>
>
> On Nov 19, 2009, at 3:53 PM, Igor Vaynberg wrote:
>
>> whats the usecase for a request-scoped variable?
>>
>> you can have a transient field on the page that you null in ondetach()...
>>
>> otherwise you can access httpservletrequest and use attributes.
>>
>> -igor
>>
>> On Thu, Nov 19, 2009 at 1:51 PM, Douglas Ferguson
>> <[email protected]> wrote:
>>> is there a best practice for request scoped variables in wicket?
>>>
>>> D/
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to