>> From: Benjamin S. Rogers [mailto:[EMAIL PROTECTED]] >> >> 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.
> While you're correct that this would get around any sort of tag/function > naming conflicts, it goes against what I understand of the intent for BD, > namely compatibility with the accepted CFML language. The alternate > naming > scheme would not do anything about splitting the core CFML language among > competing products. Although there might be a way for New Atlanta to allow their new tags to use both namespaces, i.e. <bdforward> and <cfforward> would be interchangeable as long as you used blue dragon. This could potentially ease some of those issues related to having different sets of tags per cf server vendor. S. Isaac Dealey Certified Advanced ColdFusion 5 Developer www.turnkey.to 954-776-0046 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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 Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm
