I think your best bet is to only show product titles, and possibly a bit of the summary or something in the catalogue, then have the user click the product to view full information on it. this takes 2 db calls, one to load the limited info of all products, and one to load all info on one product.
I think if you get into servlets and such, your going to run up other resource problems for the sake of saving very little. Jason "marc serra" <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I'm currently designing a website with a catalogue containing lots of > products (more than 1000). > > To reduce response time to database, I want to know if there is a solution > like loading all objects in memory for all users like a servlet could do in > java and after giving to each people connected to website a way of accessing > this "shared memory" ? > > > > I'm interested in any solution, > > > > thx > > > > Marc. > > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
