> No, CF uses a castrated version of the K2 engine. God knows what they
> castrated, other than the # docs limit.
As far as I'm aware CF uses the standard K2 OEM engine. The Verity/CF
gateway reduces some of the functionality available but at the same time
it greatly simplifies the process of connecting to Verity.
> BTW, how many companies do you know that use the CF Verity engine
> successfully?
We've implemented CF/Verity in any number of places over the last 5
years. Funnily enough we've not had a performance problem with either
the read or update functionality of Verity. Most of the time we don't
even bother to implement the K2 Search service and rely on VDK.
That said, we typically take great care to ensure that the collections
are regularly optimised and that they are efficiently updated.
I've also worked with a variety of other search products (including
Lucene) -- I'm not wedded to Verity. I just object to it being thrown
on the scrap heap when in many instances it is perfectly good, very easy
to setup and comes bundled with CF.
-- geoff
http://www.daemon.com.au/
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
