Are there any plans to allow Spectra to work with the new database schema
for userdirectories. Several tags - the cfa_group*** family, the
cfa_user*** family and probably some others make direct queries on the
userdirectory database. Since the schema has changed for CF 5 will there be
updated releases for these tags or will we have to continue to use the old
database schema for Spectra applications?
Spike
At 00:12 08/05/2001 Tuesday, you wrote:
>Yes - they will and currently do work together.
>
>Spectra does not use any of the new "features" of cf 5.0 like UDF's, QofQ's,
>etc.
>
>The only items that effect Spectra running on CF 5.0 are the new versions of
>Siteminder and Verity - and these are only new versions of the bits.
>With the exception of Verity K2, there are no additional features of these
>products that will effect running Spectra. The CFML used in Spectra is ALL
>valid in CF 5.0
>
>The main issue that I have come across in making sure they work together is
>that the new Siteminder v.411 handles user directories in a different manner
>than it did in v 3.51 (cf 4.x). In v3.51 the UD schema was stored in an
>..ini file - with v4.11 this data is stored in a database table. Not a big
>deal.
>
>The Spectra 1.5.1rc configuration wizard has been updated to accomodate this
>change - so it should be transparent to users.
>
>regards,
>peter watson
>cf & spectra qa
>
>-----Original Message-----
>From: Lanny R. Udey [mailto:[EMAIL PROTECTED]]
>Sent: Monday, May 07, 2001 5:45 PM
>To: Spectra-Talk
>Subject: CF5 and Spectra 1.5.1
>
>
>Hi,
>
>Is it safe to say that 1.5.1 will be compatible with CF5 when both are
>released?
>
>Thanks
>
>Lanny Udey
>Hofstra University
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
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.
