Also posted to ColdSpring list...
So this brings up a conundrum. 'Fixing' this may very well bring up
more problems that solutions. ColdSpring does some magic on cfc
metaData, which evidently does not work on CF 6.1 versions prior to
CF 6,1,0,83762 (which is still available on Adobe's site). In order
to make ColdSpring work with these earlier versions, I am worried
that we may be introducing problems by altering cached cfc metadata.
We have no idea what you may do with metaData on your applications,
and if we are inserting data into it, you will have unexpected
results. I'm not sure I like this solution, what do people think
about just saying CS (And this Unity) just require the latest 6.1 and
beyond?
Thanks for input!
Chris
On Jun 16, 2006, at 3:54 PM, Dave Carabetta wrote:
On 6/16/06, Dave Ross <[EMAIL PROTECTED]> wrote:
Dave,
I definitely agree. I don't want to be coding around old (this one is
from 2003!) bugs in CF. I do think it would be a case-by-case thing
though, and if this is the tiny fix that it looks like it will be, I
don't see much harm in it, as long as it's not taken as a
"precedent".
I hear you. I was thinking the same thing ("tiny fix, so no big
deal"), but Lord knows you guys have put in enough time getting the
project(s) to their current state, so I just wanted to press the point
that there's no reason for people to be below the latest patch level
for MX 6.1 in particular. I'm certainly not trying to be cutthroat
about it, rather I thought I'd chime in to help manage expectations.
Back to "lurk mode"... ;)
Regards,
Dave.
Chris Scott
[EMAIL PROTECTED]
http://cdscott.blogspot.com/
http://www.coldspringframework.org/
