I was just answering some questions about how Verity works for some co-workers when it dawned on me that most CF people don't know the inner workings. So, I thought I would share. Verity works like this. The Verity indexer is a two-part multithreaded process. Part one is that spider. In some systems you can define the number of spiders, but in most second party implementations of Verity (i.e. BV, Netscape, ColdFusion, etc...) this is not the case. The spider itself still works the same. The spiders scope is limited by the licensing. (local host only, domain only, no limit, etc...) The spider finds files, objects, whatever... and loads them into a temp space on the host machine. Again, in some systems you can define the amount of space that this process uses. Part two is the filter. The filter is a parsing script that breaks down each item and places them in the collection. There are several different types of filters that are used. There are file specific filters for .doc, .pdf, etc... The only process that I know of that is not a multi-threaded process is the filter for .pdf. (Adobe didn't write it that way for some reason) The collections are the proprietary database in which all search items are stored. There are several operations that can be performed on a collections to improve search response. Create, rebuild, restart, purge, delete and optimize are the most common in second party solutions. If you have more specific questions about your implementation, I would be happy to help. Regards, Rusher Broadiant Corporation 999 18th Street Office (303) 308-2963 Suite 1955 Cellular (720) 939-6661 Denver, CO 80202 Fax (303) 298-7540 [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> Success usually comes to those who are too busy to be looking for it. ------------------------------------------------------------------------------ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
