We've just spend a lot of time working on a JSP driven search engine for an
e-commerce project, and we're satisfied with what we have. I'm interested
to know if anyone has done anything along these lines too. My question:
how do large scale search engines instantly return the approximate number of
results? We've found this impossible to do using ResultSets. Has anyone
found a good way to do this?
----- Original Message -----
From: Ian <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, November 15, 1999 11:13 AM
Subject: How should support for scrolling large lists be designed?
> Hi Craig and all:
>
> This must be an area of concern for many people!
>
> If a site has potentially thousands of simultaneous users, each doing a
> general search that potentially has a resultset of thousands of rows - how
> should the paging/scrolling of the resultset be designed? What level of
> detail are people saving in the resultset if they use this approach?
>
> How do the major search engines support page prev/next? Are they really
> storing a session-specific resultset? Even when there are thousands of
> potential rows?
>
> I have seen a reference to one solution that advocates storing a
> second-level key to the resultset and defining a second cursor that can
> reposition at a specific page by using this key - but this seems like a
LOT
> of extra work to me, and it doesn't support paging backwards very well.
>
>
> Thanks for any ideas/experiences,
>
> Ian
>
>
> ----- Original Message -----
> From: Craig R. McClanahan <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, November 15, 1999 9:49 AM
> Subject: Re: JDBC from JSP
>
>
> > "Loganathan, Kamalesh" wrote:
> >
> > > My application is a reporting & monitoring application. Personally, I
> don't
> > > want to use any database related classes in jsp page. Instead, I would
> like
> > > to create report (wrapper ?) beans and use them in the page. But,
> should I
> > > create a bean for each row (entity) or use a manager bean as wrapper
> class
> > > for resultset ??
> > >
> > > Any comments ??
> > >
> >
> > If you are using the ResultSet, either directly or indirectly via a
> wrapper bean,
> > there are some implications:
> >
> > * The ResultSet must remain open (potentially across multiple
> > requests if you allow the user to scroll forwards and backwards
> > by pages like a search engine does).
> >
> > * Therefore, the Statement from which this ResultSet was created
> > must remain open.
> >
> > * Therefore, the Connection from which this Statement was created
> > should remain exclusively allocated to this user (to avoid problems
> > with transactional commits and rollbacks affecting the results).
> >
> > On the other hand, if you create business object beans to represent your
> results,
> > you can close the ResultSet and Statement, and return the connection to
> your
> > connection pool, as soon as the query completes. This can substantially
> increase
> > the number of users your application can support with a given number of
> > connections.
> >
> > Craig McClanahan
> >
> >
>
===========================================================================
> > To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
> JSP-INTEREST".
> > FAQs on JSP can be found at:
> > http://java.sun.com/products/jsp/faq.html
> > http://www.esperanto.org.nz/jsp/jspfaq.html
> >
>
>
===========================================================================
> To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
JSP-INTEREST".
> FAQs on JSP can be found at:
> http://java.sun.com/products/jsp/faq.html
> http://www.esperanto.org.nz/jsp/jspfaq.html
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
