The solution is not good because what if the number of records is huge?
The server will choke just attempting to retrieve them.
Lets say it actually can retrieve the records into memory (after probably
a long time), and you put them in the session. Then suddenly your
sever will break because there are thousands of (or even just hundreds of)
user accessing the page -- think how much memory it consumes with a large
collection of records...
> -----Original Message-----
> From: Nishit Trivedi [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, April 12, 2001 2:49 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Caching problem
>
>
> I don't get it.
> These are two conflicting statements you are having:
>
> 1."But i dont want to retrive all record at the same time
> sothat it will take a lot of time for the first time."
>
> 2. "also not want to
> connect to dastabase for each request for next 25 records."
> Question are:
> 1.How can you get another 25 without connecting AGAIN to db..???
> 2.And how you are going to keep track which one was selected at
> first time and which ones are not...??? (unless you want to
> delete records
> from db as soon as they are selected)
>
> But here is what i think :
> You can use session for it...
> Get all result from db at a shot and store it in an array
> (well if you dont
> know exactly how many records are there then first store it
> in vector and
> then convert that vector into array)
> Now store that array in a session..
> Now when user selects let's say 1 to 25
> records,display records 1 to 25 and so on...
>
> hope this may help you..
> Nishit
>
>
> -----Original Message-----
> From: Debasis Dash [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, April 12, 2001 5:13 PM
> To: [EMAIL PROTECTED]
> Subject: Caching problem
>
>
> I am requesting aquery which return 5000 results. But i want
> to show only 25
> record per page. But i dont want to retrive all record at the
> same time
> sothat it will take a lot of time for the first time. also
> not want to
> connect to dastabase for each request for next 25 records.
> How to build the
> caching mechanism for this.
>
> ==============================================================
> =============
> To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
> JSP-INTEREST".
> For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST
> DIGEST".
> Some relevant FAQs on JSP/Servlets can be found at:
>
> http://java.sun.com/products/jsp/faq.html
> http://www.esperanto.org.nz/jsp/jspfaq.html
> http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
> http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
>
> ==============================================================
> =============
> To unsubscribe: mailto [EMAIL PROTECTED] with body:
> "signoff JSP-INTEREST".
> For digest: mailto [EMAIL PROTECTED] with body: "set
> JSP-INTEREST DIGEST".
> Some relevant FAQs on JSP/Servlets can be found at:
>
> http://java.sun.com/products/jsp/faq.html
> http://www.esperanto.org.nz/jsp/jspfaq.html
> http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
> http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
>
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
