Johan,
Please enlighten me - what is the application object that you refer to? Is
it just a single entity EJB that maintains common state - ie caches,
application settings etc? Is there some discussion of it anywhere as an
element of J2EE application design?
Thanks,
Andy
----- Original Message -----
From: "Johan Fredriksson" <[EMAIL PROTECTED]>
To: "Orion-Interest" <[EMAIL PROTECTED]>
Sent: Wednesday, March 28, 2001 8:17 AM
Subject: Re: Paged search results
> My first thought is that a cache should not be stored in a session, since
> that would only be available in that session and "cannot" be shared...
> Better to store a searchresult in the application object ( if the result
is
> static and is the same for all users). If the searchresult is specific to
a
> certain user, then you could store it in a session.
>
> For multibrowser usage, there will be separate sessions for those. There
is
> probably a way to get them to use the same session, but I haven't tried
> this. In this case I suggest a hashtable in the application object and an
id
> string ( key in hashtable ) in the session.
>
> Hope this at least gives you a couple of ideas on how to get started.
>
> regards
>
>
>
> Johan
> ----- Original Message -----
> From: "Holden Glova" <[EMAIL PROTECTED]>
> To: "Orion-Interest" <[EMAIL PROTECTED]>
> Sent: Wednesday, March 28, 2001 6:19 AM
> Subject: Paged search results
>
>
> > Hi all,
> >
> > Perhaps this is slightly off topic and
> > if so, I apologize and feel free to
> > ignore this. My knowledge of j2ee is not
> > high but I would like to know the best
> > way to handle this with of course,
> > minimal complexity. I am not sure where
> > else I can find information on this
> > subject from knowledgeable people
> > though, so here goes.
> >
> > We are wondering what the best approach
> > would be move through a collection of
> > page results that come back from a
> > search. We have thought about using
> > sessions to cache the results and help
> > keep track of what the current result
> > view consists of, but we are not sure if
> > this is the best way to handle something
> > like this. Some things that come to mind
> > are what would happen if we have
> > multiple browsers open trying to perform
> > different searches at the same time,
> > would we need a separate SessionBean to
> > cache these results in?
> >
> > What could be some of the advantages and
> > disadvantages of using sessions for this
> > problem? Can anyone point me to some
> > other ways of approaching this problem
> > aside from using sessions?
> >
> > Thanks in advance for any help and
> > pointers that are given.
> >
> > Regards,
> >
> > --
> > Holden Glova, [EMAIL PROTECTED]
> > Software Engineer
> > Alchemy Group Limited
> > Level 6 Royal Sun Alliance Bldg
> > PO Box 2386
> > Christchurch
> > New Zealand
> > Phone: +64 3 962-0382
> > Fax: +64 3 962-0388
>
>
