> Ah, didn't realize that about VDK. We definitely need > to use cf tags to update the collections, so that would > also rule out k2.
It needn't rule out K2; you just have to use VDK for indexing and K2 for searching. You can have VDK index the collection, then use K2 to search it. A collection is essentially just a directory, so you could have one collection name you use for VDK indexing and another for K2 searching. Actually, you typically have two collections in K2 for each VDK collection, since K2 collections map to the file and custom subdirectories of the collection directory. The issue in a clustered environment, though, is that you'd need to have the directory accessible by whichever server is going to run CFINDEX. It's not an insurmountable issue, though. > We will be adding collections periodically, and the > process really needs to be automatic. We could probably > automate the editing of the k2server.ini file and the > restart of the k2 server, but that just sounds really > ugly. It's not as bad as it sounds. The CommonSpot product, for example, does this very nicely. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
