Vince, > I'm not sure I understand what you're saying. Are you saying there are > existing incompatibilities in BD 6.2 that you'd like to see fixed before > we add these enhancements?
There are existing incompatibilities. I would like to see them resolved, but I don't think that's going to happen: many of these incompatibilities are by design. For instance, BlueDragon introduces tags in the "cf" namespace instead of providing a separate "bd" namespace or importable tag lib. The functionality of other tags has been changed: the suppresswhitespace attribute of the cfprocessingdirective tag transcends page scope and aggressively strips white space from code. And there are some features which New Atlanta has just ignored. Sandbox security, though imperfect, is pretty much a necessity for shared hosting environments. > Or, are you saying we shouldn't add these > enhancements because they themselves are incompatibilities with CFMX? I'm saying that I would have preferred if New Atlanta had added these enhancements in a way that did not break compatibility with ColdFusion. For instance, you could have placed tags like cfimage and cfimap in a tag lib that we could then import into a neutral namespace. For a fee, you could have then licensed the tag lib to third party developers for redistribution. That way, they could embed the tag lib in their applications and more easily distribute applications compatible with both BlueDragon and ColdFusion. Right now, it seems very few third party apps support BlueDragon. If they do, there's almost always a separate code base. Subtle changes like that to cfprocessingdirective means there's a good deal of debugging and head scratching involved in supporting BlueDragon if you're coming from ColdFusion. > If the former, then I'd like to know what existing issues you have with BD > 6.2 so that we can fix them. I've mentioned much of this already on the BlueDragon mailing list. I don't think you have any intention of fixing it because you don't see it as a problem. > If the latter, then I'll respectfully > disagree; we plan to move forward with these enhancements regardless of > what CFMX does. That's your prerogative. I don't see how a business model based on splintering the ColdFusion development sphere works, but you're free to try. However, we can't switch our hosting customers to BlueDragon because of incompatibilities in existing tags and functionality. Just to be clear, I really like some of the features New Atlanta has added. Cfimage, cfimap, the "website" attribute of the cfsearch tag, etc. Those are all great enhancements. I've used BlueDragon on my own box to accomplish a few things that would have been difficult or required third party custom tags. I just wish compatibility was a high priority for BlueDragon. Ben Rogers http://www.c4.net v.508.240.0051 f.508.240.0057 ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
