I'm all for added functionality/tags/functions, but I also understand the concerns. I would think, however, that Macromedia implementing a tag called cfforward which did not function exactly as New Atlanta's would be just as big of a problem for New Atlanta as for their customers, whether they are developing for both environments or migrating from one to another.
A way to minimize the problem would be for New Atlanta to use a different namespace (so to speak) for their tags. I'm not talking something as complicated as XML namespaces, but simply using a different naming scheme, such as <bdforward>. Ostensibly, ColdFusion would ignore these tags when validating/processing a page so their presence in the page would not immediately generate an error. As for the possibility that Macromedia would adopt these new tags, I won't hold my breath. They may implement the functionality, but I doubt it would take the same form. There's simply no reason for Macromedia to architect CFML around the alternative implementations of third parties, and they've shown no interest -- at least not that I'm aware of -- of standardizing CFML. In fact, if history is any guide, it would behoove them to do just the opposite, take the Microsoft approach (DRDOS and OS2) and break compatibility wherever possible. I personally doubt they will do this, however. There position in the CF market is secure. There's no need to resort to such tactics. Benjamin S. Rogers http://www.c4.net/ v.508.240.0051 f.508.240.0057 -----Original Message----- From: Hugo Ahlenius [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 15, 2002 9:36 AM To: CF-Talk Subject: RE: BlueDragon (was RE: How is CFMX J2EE implemented?) | -----Original Message----- | From: Ken Wilson [mailto:[EMAIL PROTECTED]] | Not exactly. Custom tags can be easily copied to another server. That | can't be said for something that is integrated into the server itself. | So any app that relies on that functionality breaks if it | gets moved to | another variation of CF Server. Well, a lot of customtags depend on platform-specific out-side executable (windows/linux only), COM-objects, or platform-bound CFX tags. Using CF 4.5 on Solaris (or linux I guess), you get very aware of this -- when you hunt around for customtags you have to look carefully! /h. ########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm
