Just saw the thread maybe I can help.
First thing to realize is how CF knows the difference between a k2
collection and a local collection. for backward compatibility if your
collection is located locally to the server it uses the same verity'97
engine. But if you accessing a collection on a k2 server (any cf server
except the local one) it uses the k2 engine. There is also a naming
difference, but I'll get to that.
so when you do a search on collectionA CF will first check local. If it
exists it searches that using the verity'97 engine. But if it doesn't and
you have a k2 server IP defined it will see if the collection exists on the
k2 server. if not, error. But if so it will search against that using the k2
engine. nice and simple.
So what's local on one server is a k2 collection for another server. For us
the collection name is simple "CollectionA" but for the server it has the
type of collection appended, CUSTOM or FILE. example: "CollectionA_CUSTOM".
So when you searching "collectionA" it will check the different server. But
I believe, NOT TESTED, you can actually use the full name with the type
appended to differentiate the collections and force the use of the k2 if you
have your k2 IP the same as the local server, for instance. just by putting
in "CollectionA_CUSTOM" as the collection name, in the cfsearch and cfindex
tags.
Now to make Spectra work with the k2. You need to dedicate a server to be
the collection server. And make sure you use that server to do the
<cfa_typeindex> and other indexing tags. and don't bother building your
collections on any of the other spectra servers, because then the k2 version
won't get used. Doing this will make the spectra search tags will
automatically use the k2 version.
But remember the search tags where never (or at least not extensively
tested) against the k2 server. So you might find oddities (this is a
disclaimer, I haven't found any personally). and the validation inside the
cfa tags, might not let you get away with all the newer feature of the k2
engine (xml, etc). so you might have to switch your searches to use the
<cfsearch> tags directly. but that's minor right ;-)
Hope this helps explain the k2 server and spectra a little.. Most of this
was from memory when I was working with the developer to figure out what
functionality the cfadmin k2 pages needed. I'm apologizing ahead of time in
case I've remembered something a little different then it is.
---nimer
-----Original Message-----
From: Doug Cain [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 12, 2001 8:16 AM
To: Spectra-Talk
Subject: RE: Spectra + Verity K2
Looks like this tread has died a death with no particular resolution.
This seems to happen consistently when talking about verity.
Any input from macromedia would be appreciated.
Doug Cain
The Online Courseware Factory
-----Original Message-----
From: Darren Nickerson [mailto:[EMAIL PROTECTED]]
Sent: 11 September 2001 01:54
To: Spectra-Talk
Subject: Re: Spectra + Verity K2
Folks,
Thanks for the feedback! Once the houseoffusion.com mailserver came back
up
after its weekend sojourn it was good to see a few pickups on this
thread
(which is on crack - loved that one Geoff).
Bottom line seems to be that this is not supported without code changes
to
Spectra itself, which would not be trivial and certainly out of our
reach in
the short term.
It would be nice if Raymond or another Macromedia rep would chime in on
this
one, but even in the absence of that it looks like we're going to have
to
deploy VDK mode, and try to back-pedal when/if anyone manages a proof of
concept with K2 server.
What a shame :-(
-Darren
--
Darren Nickerson
Chief Technology Officer
iWorkwell, Inc.
215.875.9550 (voice)
215.882.3266 (cell)
215.243.8335 (fax)
HR Made Easy.(tm)
The information contained in this email message is intended only for the
personal and confidential use of the recipient(s) named above. This
message
may contain confidential and/or privileged material. If the reader of
this
message is not the intended recipient or an agent responsible for
delivering
it to the intended recipient, you are hereby notified that you have
received
this document in error and that any review, dissemination, distribution,
or
copying of this message is strictly prohibited. If you have received
this
communication in error, please contact the sender immediately, and
delete
the original message.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Get the mailserver that powers this list at http://www.coolfusion.com
------------------------------------------------------------------------------
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.
