I think we ended up fixing the coapi in that other case. I'll let you know what we end up doing here as well- defensive COAPI seems like a good idea to me. -c -----Original Message----- From: David An [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 19, 2000 12:16 PM To: [EMAIL PROTECTED] Subject: RE: another case-sensitivity issue Sean - Yes, I could - and that's what I ended up doing. In the end it was a very easy fix. My consternation was really caused by the fact that one COAPI tag (contentObjectGet) worked and another didn't (contentObjectData). I guess I'm just looking for some consistency. I admit that it was my mistake in passing a lower-case ID (though I gotta blame some of it on Flash) but I would like to see the COAPI tags acting the same way. -- David At 09:06 AM 7/19/2000 -0700, you wrote: >David, > > I may be way off as I am pretty fresh to Spectra but couldn't you > just >ucase() the input??? > >Sean O'Brien >CTO, The Bike Company >http://www.bikeco.com > >-----Original Message----- >From: David An [mailto:[EMAIL PROTECTED]] >Sent: Wednesday, July 19, 2000 8:19 AM >To: [EMAIL PROTECTED] >Subject: another case-sensitivity issue > > >I've been working on a pretty convoluted project. In a couple instances, >I'm using Spectra via publishing rules to retrieve one or more >objectIDs. An ID are then passed into a Flash movie, and via Flash's >ability to "include" additional Flash movies, the ID is passed through a >couple movies, and then Flash calls back to Spectra. > >Somewhere along the way - and I'm 99% certain this is a bug/feature of >Flash - the ID was lower-cased. When Flash passed it back to Spectra, I >was attempting a contentObjectGet, manipulating the object, and then saving >it via contentObjectData. The contentObjectGet worked with my lower-cased >ID, but the contentObjectData did not. > >While I realize that this is not really a shortcoming in Spectra, wouldn't >it be nice if Spectra coded defensively against this in *all* tags, not >just some? Or, on the other hand, if I pass in a lower-case, and therefore >invalid ID, should I not expect results? > >In an earlier thread I noted a problem with case-sensitivity in the default >"search" publishing rule, and Charles mentioned that for a later release, >either the rule or the contentObjectData tag would be fixed (or both). I >guess I'm putting in my vote here to "fix" the COAPI tags to be coded for >case-insensitivity. > >BTW, I've updated my own contentObjectData tag - it's a simple fix. Just >add one statement at line 86: > cfset attributes.objectID = UCase(attributes.objectID) > >That's all! > >-- David > >------------------------------------------------- >David An: [EMAIL PROTECTED] >-- life through a browser -- >MINDSEYE Technology, Inc. http://www.mindseye.com/ > > >--------------------------------------------------------------------------- - >-- >To Unsubscribe visit >http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_tal k >or send a message to [EMAIL PROTECTED] with >'unsubscribe' in the body. > >--------------------------------------------------------------------------- --- >To Unsubscribe visit >http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_tal k >or send a message to [EMAIL PROTECTED] with >'unsubscribe' in the body. ------------------------------------------------- David An: [EMAIL PROTECTED] -- life through a browser -- MINDSEYE Technology, Inc. http://www.mindseye.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. ------------------------------------------------------------------------------ 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.
