Looks like we are the only ones. Steve is also lurking. And you should seriously consider caching any time it can be of use - even if the query is cached for minutes only. CF makes it easier and it can give the server a breather.
However remember the "scopes" you can use for caching. In some cases "session" might be sufficient. In others application or even server level might be more appropriate. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Taco Fleur Sent: Sunday, 1 February 2004 2:34 PM To: CFAussie Mailing List Subject: [cfaussie] Re: Efficient Paging - follow up on an old post Hi Peter, Not sure whether I understand your post or whether you understand mine ;-)) But the method I am proposing does not use cached queries at all. Cached queries is nice for little apps, but as you say yourself its limited to a certain amount of cached queries, thus not the ideal method for a heavily used search interface. Even so, a cached query transfers ALL data in the resultset to the app, the method I am proposing/using does not transfer any more data than required upon each request. Where the [EMAIL PROTECTED] is everyone? are we the only ones working in the weekend? Taco Fleur Blog http://www.tacofleur.com/index/blog/ Methodology http://www.tacofleur.com/index/methodology/ Tell me and I will forget Show me and I will remember Teach me and I will learn > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Peter > Tilbrook > Sent: Sunday, 1 February 2004 1:20 PM > To: CFAussie Mailing List > Subject: [cfaussie] Re: Efficient Paging - follow up on an old post > > > Caching the query for "paging", ie next 10 records, previous 10 > records, firs page, last page, is a great idea. > > But take this into account first: > > How "dynamic" will the list be - if not altogether dynamic - great. > > Otherwise - if the database data is changed, force a database > "refresh" to the same scope as your cached query to ensure the end > user is seeing the up-to-date information. > > Apart from that this method can really help your application > performance, as long as you respect the amount of memory you server > has and the limit of (100 cached queries I believe - limited by the > servers memory - 1 cached query could kill it) that CF has for this. > > --- > You are currently subscribed to cfaussie as: > [EMAIL PROTECTED] To unsubscribe send a blank email to > [EMAIL PROTECTED] > > MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004 --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004 --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
