Caching a query and using the blockfactor to employ a "Get next n records" is a really easy thing to implement. Its easy to code, easy to use, easy to maintain, easy to understand....i guess i dont see where the complexity comes in?

  ----- Original Message -----
  From: Micha Schopman
  To: CF-Talk
  Sent: Friday, July 30, 2004 8:11 AM
  Subject: RE: The search is killing the server. Please help!

  So because something is more difficult to do, we just take the situation
  which causes the most overhead on the server and stores duplicate data.
  Session variables can get you faster into trouble then application
  variables because the CMFX garbage collector is only called once a time
  and not on each request. So it is very important to minimize this types
  of situations :-)

  Micha Schopman
  Software Engineer
  Modern Media, Databankweg 12 M, 3821 AL  Amersfoort
  Tel 033-4535377, Fax 033-4535388
  KvK Amersfoort 39081679, Rabo 39.48.05.380
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

Reply via email to