>option 2 and 3 are overheads for a large app
This is an overstatment. The real question is whether This overhead causes
major [performance, etc] problems for THE app , u are working on [not any
large app], or not. And that is the question which you can only answer.
regards,
RajibJana wrote:
>option 2 and 3 are overheads for a large app, I will check option 3 ,
>currently I am using glassfish, will check whether option 3 is available >in
>gf.
Struts Two wrote:
>
> There are a few solutions to your problem:
>
> 1- You can serialize your object as a hidden field and deserialize it on
> each request if you need it. It serves like a baggage that you carry form
> page to other. In this way, you avoid putting any object in session scope.
> Some folks may argue that this is not efficient for huge-sized objects,
> but keep in mind httpsession should not be confused with storage. I
> already use this solution in a few medium size webapps, works like charm.
>
> 2- If the object put in session is sort of object like ,say, the one the
> holds user credentials, roles, timezones, etc that can be calculated at
> each request, you may have custom interceptor that does it each time a
> user submits a request. You may incur just an extra cost of going to
> databse, to get all the information but with today's hardware speed and
> software, you should not worry about that. I have also used this solution
> and it also works like charm.
>
> 3- [I have not tried this myself ], If you are using servers like
> websphere, they provide other ways of session management except cookies
> and url rewriting like using ssl id for session management. You may want
> to try it.
__________________________________________________________________
Looking for the perfect gift? Give the gift of Flickr!
http://www.flickr.com/gift/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
