Erik,
One way to do it is:
1) Keep a list of fuseactions in a database table (this is something I do by
default)
2) Loop through the fuseactions and use CFHTTP to grab the pages that result
from each fuseaction
3) Make a "fake" query useing Querynew, QuerySetCell, and QueryAddrow.
4) Use CFINDEX to index the fake query, the key or a custom field is going
to be the fuseaction so that when someone searches, they can be dumped back
to the correct fuseaction.
Because this can be a slow process, you might want to use some kind of
timestamp to keep track of what pages have been updated and which ones not.
Only index the ones that have not been updated "Recently"
There are other ways to do it, but this is one, and it does work.
Eron
-----Original Message-----
From: Erik Voldengen [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 19, 2000 7:41 PM
To: Fusebox
Subject: Verity and Fusebox, Revisited
Is anyone working on a Verity/Fusebox site solution for
performing site searches? There were a few posts from
interested parties, but I'm not sure if anyone actually
started anything.
I've got some good ideas as to how this can work, so if
nobody is already working on it, I think we (HMweb) will
take a stab at it in early January. Anyone who'd like to
participate is welcome, just email me off the list.
__
Erik Voldengen 6740 N Oracle Road, Ste 100
Lead Developer Tucson, Arizona 85704
HMweb 520-742-2611 ext. 111
www.HMweb.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
