A JCP-like process for standardizing CFML would prevent such a thing from happening. Hopefully, if such a hypothetical event did happen, then enough of our customers would scream at us and enough of Macromedia's customers would scream at them, that we'd get together and fix it. (For many different valid reasons, a lot more of Macromedia's customers are going to have to scream at them, a lot louder, to get them to move on creating a JCP-like process for CFML).
Vince Bonfanti New Atlanta Communications, LLC http://www.newatlanta.com > -----Original Message----- > From: Jochem van Dieten [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, October 15, 2002 9:22 AM > To: CF-Talk > Subject: Re: BlueDragon (was RE: How is CFMX J2EE implemented?) > > > Vince Bonfanti wrote: > > <snip>a lot that I like</snip> > > > 3) Any CFML enhancements introduced by BlueDragon are proprietary > > and are not part of the CFML standard, and will be clearly > documented > > as such. Of course, we will be delighted if/when Macromedia > adopts any > > of our enhancements as official parts of the CFML standard. > > But, purely hypothetical, what happens if you release > BlueDragon version > 4 a few days before Macromedia releases ColdFusion XXL and BlueDragon > has a tag cfwhatever that does X and CF XXL has a tag cfwhatever that > does Y? > > Jochem > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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 Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm
