Bye Bye Clear!

Wow: Clear, operator of registered traveler lines in many airports around the country, has ceased operations. For more (what little there is) visit http://www.flyclear.com.

I liked Clear and I'm disappointed it has shut down. There are numerous new stories about the shut down and most of them indicate that the Clear lines were idle much of the time. When you're using them, they are, by virtue of your usage, not idle--but still, thinking back on it now, there were times when I was the only person going through.

So why were the Clear lanes idle so much of the time? Because their value proposition wasn't clear (pun intended; ha ha!) for enough people. As mentioned in an Atlanta Business Chronicle article the wait time at the "regular" lanes here in Atlanta is rarely more than 10 minutes; I didn't note any other statistics for other airports in any of the other articles I read, but many of them did mention in general terms that security wait times are generally modest these days. And, as numerous of the news articles indicate, the Clear security screening process itself is no easier or quicker than the regular security screening process--rather it is the same process as in all other security lines. So if you aren't saving hassle with the actual security screening and you aren't saving significant waiting time, what are you really getting from Clear? It seems most people answered that question with one word: "nothing." Hence, even a clear (I can't help myself!) path through the Clear lines wasn't good enough to attract new customers. And I'm sure that as they looked to prospects for the future, what they saw is that the worst part was that if they had somehow been able to grow, the reality is that they would have only been able to handle a certain amount of growth (at least without expanded capacity) before they'd actually have found themselves into a situation where their wait times frequently exceeded those of the regular lanes!

So with this all being the case, why was I a Clear member? Well, when I joined last year, regular security lines were generally longer than they are now. Why has this changed? Since that time, the economy has weakened and less people are flying, and at some airports like Hartsfield-Jackson Atlanta International Airport, additional regular security lanes have been added, plus it seems that people are moving through security faster than they did last year (I'm not entirely sure if this is true or if it is, why it is, but kudos to TSA for any role they've had in the matter). But regardless of the reasons for the reduced wait times in the regular lines, I was contemplating not renewing at the end of my current membership period as a result of those reduced wait times. And you may find it surprising to find that I was actually leaning towards renewing. Why? Because even if Clear didn't provide actual speed advantages over the regular lanes, it did provide certainty of speed. That is to say, it provided a certainty that you'd get through security fast. So now the position I'm in is that when I go to the airport on Wednesday morning, I'm probably going to get through security quickly--but since I no longer can rely on that, I'm going to have to arrive earlier than I would have if I were able to use Clear--and the worst part is that I'll still be at greater risk of missing my flight! And that, my friends, is why I will miss Clear.

P.S. Although Clear ceasing operations rips off any existing Clear member, the good news for me is that although I had a bit more than 5 months of membership left on my term, I did still get much of the expected value out of my Clear membership: I purchased a 1-year membership in March of 2008 and had gotten additional bonus time from a pre-Atlanta-Clear-lanes opening special and from others using my Clear referral code. But surely there are some people who only recently had paid for Clear memberships; such people were supremely ripped off. But it pales in comparison to the investors who lost millions, right? Well, if Clear intentionally deceived those investors then yes--but otherwise, those investors simply invested in a company which just didn't pan out, they weren't ripped off like us Clear members were.

P.P.S. On a slightly related note: once, during the course of normal use of the Clear website (that is to say, not during a web application security penetration test), I stumbled upon a web application security vulnerability through which an attacker could have harvested Clear customer email addresses (to be clear, the attacker would only have been able to do this harvesting of email addresses one by one, not en masse; as for other details, well, as Forrest says, that's all I have to say about that). I always was amused by the irony of a company which went to great lengths to keep personal data safe having such a hole on their website! And I always wondered when Clear would discover the hole and patch it (but that certainly appears to be a moot point now!). I believe a good web application security assessment would have revealed this vulnerability and so I therefore find it doubtful that Clear authorized such an assessment. But regardless, this vulnerability just goes to show that even companies like Clear are not sufficiently adept at precluding unauthorized access to customer data. Feel free to shudder.

Heading to Estonia!

I'm heading out today on a short-term mission trip to Estonia! You can read more about it at http://www.estoniax.com/josh and you can follow our team's blog (hosted by my good friends at FusionLink and running on Mango Blog) at http://blog.estoniax.com. But don't worry--I'll be back to Atlanta in time for the ColdFusion 9 + Flex 4 User Group Tour meeting with Ben Forta!

ColdFusion 8 Enterprise or Standard?

How do you decide between ColdFusion 8 Enterprise and ColdFusion 8 Standard? Start by attending my Adobe eSeminar "The Right Fit: Adobe ColdFusion 8 Enterprise or Standard" to be held on Wednesday, April 29, 2009 at 11:00 AM PST. I hope to see you there!

Learn about ColdFusion + the Flash Platform (including Flex & AIR) LIVE in DC!

Want to learn more about ColdFusion + the Adobe Flash Platform? If you're in (or can be in) Washington, D.C. on this Thursday, February 10, 2009, check out the Adobe Day we're holding @ Hotel Palomar in Washington, D.C. starting @ 10:00 AM. For more information and to RSVP, visit this URL:

http://www.adoberegistrations.com/adobedays/2009/DC/AdobeDay_DC_CF.html

Unfortunately, they don't have the schedule at that URL but good news: I have that information! Here is what is currently planned:

  • 9:15 AM - 10:00 AM - Registration and Continental Breakfast
  • 10:00 AM - 10:15 AM - Kickoff and Introductions
  • 10:15 AM - noon - Adobe Flash Platform – Overview and Demos
  • noon - 12:30 PM - Lunch
  • 12:30 PM - 1:00 PM - Leveraging ColdFusion and Flex To Create RIAs
  • 1:00 PM - 1:45 PM - ROI of Rich Internet Applications and Success Stories
  • 1:45 PM - 2:00 PM - Q&A and Best Practices

Adobe Platform Evangelist Ryan Stewart is currently scheduled to be driving the content of the event.

Adobe eSeminars for 2009 Quarter 1

One of my roles at Adobe is to present eSeminars (online seminars via Adobe Acrobat Connect) related to ColdFusion. Join me, won't you? I will be presenting the Adobe ColdFusion 8 eSeminar Series for 2009 Quarter 1 over the next couple of months; details for dates, times, and topics can be found via this URL:

http://www.adobe.com/cfusion/event/index.cfm?event=detail&id=1345643

Speaking of eSeminars: you might also be interested in the Adobe Flash Platform eSeminar series for Adobe AIR and Flex developers; details can be found via this URL:

http://www.adobe.com/cfusion/event/index.cfm?event=detail&id=462539

If there are any topics you'd like us to consider for future eSeminars, please let me know via a Comment on this entry.

Book One-Way Airline Tickets Instead of Multi-Destination Tickets

Okay, this one is way off-topic in relation to what I usually blog about, but I fully believe it's going to prevent someone who reads it from making the same mistake I made. Specifically, I believe it is going to prevent someone from booking a multi-destination ticket in the situation where, for the very same total price, that person could instead book each leg of the journey separately.

So why is it a mistake to book a multi-leg itinerary instead of booking separate one-ways, if the cost of the two is the same? I'll get to that in just a moment, but before I do you should know that in the majority of cases I have seen for the last many years, at least in regards to travel within the United States, both types of booking do in fact cost the same. That could vary from market to market, but in my experience, market is not generally a concern.

Okay, so let's talk about why you always want to go with booking your flights separately, so long as it doesn't cost you any more than booking them as a multi-leg trip (actually, after you read this post, you might decide it is even worth paying a little bit more in some situations): because it gives you more flexibility to alter your travel without incurring airline change fees. And if you haven't tasted any of the change fees being charged by airlines these days, let me just tell you that they taste very, very bitter and you very, very much want to avoid incurring them. I believe that most airlines are now charging $150 for any change.

Here's the deal: if you change a particular flight on an itinerary, the effect is that every flight from that point onward on the ticket has to change too. That doesn't mean you have to make any changes to any other flights, it just means that they get priced as if they were changed. And that means that if those flights have become more expensive, you have to pay the difference between what you paid and what the new rate is. So to be clear, even if you aren't changing any subsequent flights, they "act" as if they are being changed and the price for them gets recalculated and you pay the difference between the new price and what you paid.

So you should already see where it benefits you to book separate flights: if you change a one-way flight, there are no subsequent flights so you won't have to pay any fare increases that affect flights you don't actually want to change. So if you book an outbound flight and a separate return flight and then you change the outbound flight, while you'll have to pay $150 plus any fare increase for changing that outbound flight, you won't get stuck paying any fare increase for the return flight.

To make this perfectly clear, let's consider a simple example: you pay $300 for an outbound flight and separately you pay $200 for a return flight. Then you need to make a change to your outbound flight. Unfortunately, the fare for the new flight is $350; you now have to pay the additional $50 that this new flight costs over what you paid. In addition, you have to pay $150 to make the change. Ugh. You're out $200! But what if you'd booked a round-trip? The answer is that, best-case scenario, you'd be out the same $200 because of the same fees; worst-case scenario you'd be out not only that $200 but also much more because you would also have to pay any fare increases affecting the return flight: let's say that instead of $200, that same flight now costs $250; you'd have to pay the $50 that the return flight--the same return flight, mind you--costs over what you paid for it previously. This is an absolutely ridiculous policy, by the way. But it is in fact the policy.

Ah, but it gets worse: there's another policy that says that if you don't take a flight on a ticket, all other flights on that itinerary are cancelled (you get to keep their value, minus that same hefty change fee, but you can't actually fly them as scheduled). Why does this matter? Because in the world of $150 change fees, sometimes it makes the most sense to simply bail on a scheduled flight and book a new one. Think about it: if it costs you $150 to change a flight then so long as you can buy a replacement flight for less than $150, aren't you better off buying the replacement flight and simply not taking the existing flight? Of course you are. And with multiple one-way tickets, you have the flexibility to do that in all cases; with multi-leg trips, you can only do it where it won't be a negative impact to cancel all remaining flights on the ticket (so for instance, for the last flight on a ticket). By the way, the fact that you can't take a flight in an itinerary simply because you missed other flights in that itinerary is yet another ridiculous policy, but here again, it is in fact the policy.

So another example: let's say you pay $100 for an outbound flight and $200 for a return flight then you need to make a change to your outbound flight. Good news: the new flight also costs $100; you won't have to pay an increased fare. But should you change that outbound flight? No way! You should simply skip it and book the new flight you want for $100! Why pay $150 when for $100 you can achieve the same desired result (which is a ticket on the new flight you want)? But of course, if you have other flights on that ticket (that is, if you booked a multi-leg instead of multiple separate one-ways), you can't do that because they won't let you get on any flight on an itinerary on which you have missed a preceding flight. That means that if you really want to make the change, you have to pay the $150 change fee--but remember, you also have to pay an additional increase in the fare of your return flight, even if you don't change your return flight in any way. So, let's say that return flight is now $275 instead of $200; you have to pay not only the $150 change fee, you also have to pay the $75 by which the return fare has increased. That means you're coming out paying $225 additional--and this to change a ticket that originally cost you only $300! But if you'd booked separate tickets, you'd have paid only $100 because you'd have simply bailed on your original outbound ticket and bought a new outbound ticket.

I'm actually in very much this situation right now: if I had separate tickets for an upcoming trip, I could bail on the outbound ticket and buy the flight I actually want for $105, but if I change the round-trip ticket I have it will cost me $235. It actually would cost me less money, a total of $210 for a $25 savings, to go ahead and take my original flight then immediately take the first flight back home--and the logistics of doing that actually would work out for me. Now, you may say "don't be crazy--spend the $25 extra and save yourself the hassle of the travel. And it's a valid point because while I, like everyone, would rather get something for my money, in this case I don't need it and it's actually more of a hassle to use it than it is to not use it. Ah, but by using it, there is something I would get: miles. And those miles, coming as they would at the beginning of the year (a.k.a. the point at which earning miles for elite status resets), could months down the line be just what I need to achieve the next level of elite status (and at the very least, they would get added to my total available for redemption for award travel).

So in summary, there are two places where in making changes to airline tickets you can get zinged by having bought a multi-leg ticket instead of multiple separate one-way tickets:

  1. In having to pay the change fee where you would like instead to replace a flight in the itinerary with one costing less than the change fee, but where such a replacement would mean that subsequent flights in the itinerary that you do not want to change and do want to take would be automatically cancelled when you missed your originally scheduled flight.
  2. In having to pay for the increased fare of flights for which you are not actually making any changes, simply because these flights have their fares recalculated every time a change is made to any preceding flight.

So...book multiple one-ways instead of multi-legs. Enjoy the flexibility!

QED.

I do want to make it explicitly clear that it is only in the case where you want to change a flight in an itinerary that has subsequent flights you do not want to change where it is to your advantage to have booked those flights separately rather than as part of a single ticket; in cases where you only want to change the final flight on an itinerary, it makes no difference whether that flight is a one-way or part of a multi-leg. The reason is that effectively, the final flight for an itinerary is a one-way: changes to it don't cause you to be subject to paying the fare increases of subsequent flights because there are no subsequent flights and if you bail on it, there are no ramifications in regards to the automatic cancellation of subsequent flights because again, there are no subsequent flights. Now, if you need to change multiple flights on the same itinerary, you may well be better off if you bought all of those flights as part of the same ticket because you will only be charged a single change fee to change them whereas if they were on separate tickets, you would be charged a change fee for each ticket. However, I think it is a lot more common that you need to change only a single flight than it is that you need to change more than one flight on an itinerary so I believe that it will more often benefit you to book each leg of a journey separately than it will to book those legs together.

Movie Review: "Eagle Eye"

I've never written a movie review before. And I may well never write another. But I saw "Eagle Eye" at one of those pre-screenings on Wednesday night and as such I saw it before most everyone else so I thought I'd take a minute here to let you know what I thought about it in the hopes it might be informative to you.

Now, my goal here isn't to be objective or to evaluate the movie on any particular set of criteria--I'm simply going to tell you my thoughts. Note that I cannot be held responsible for any irreparable damage this may cause. ;P

Here's the thing about this movie: the villain is a computer. Specifically, the antagonist is a computer that has become too smart for its own good and is now trying to do things that the humans in the movie consider to be nefarious. These include wearing white shoes after Labor Day, swimming immediately after eating, and killing people. Silly computer--tricks are for kids! Okay, so the computer doesn't have feet on which to wear shoes and it doesn't appear to have any interest in either eating or swimming, but it sure ain't kidding around on that whole killing people thing!

Let me say this: I like Terminator as much as the next guy. But that's set way in the future. And that machine at least acts like a dude. The computer in Eagle Eye, on the other hand, isn't all that different from the computers we're all used to, only except this one is ginormous, has these befuddling infrared innards which Hollywood apparently thinks will impress people with their complexity, and oh yeah--is trying to kill people (and I don't want to hear about how your computer seems to be trying to ruin your life by crashing at all the wrong times--it's not the same thing). The computer in Eagle Eye isn't at all like a dude--it does talk, but it has no face, no body, and it can't move around under its own power. Actually, it does have a bit of a thing for car chases so maybe it's a little like a dude after all.

So anyway, much as I like Terminator, I don't like movies set in the present day where the main difference between our actual world and the world depicted in the movie is that in the movie there's a crazed computer bent on destruction. Eh, I suppose that if the crazed computer were some minor plot line, I could hang with it if the rest of the movie were interesting, but when the crazed computer is core the entire story of the movie, I'm pretty much done. Because I was with my girlfriend and I simply don't like giving up on things, I hung in there with Eagle Eye for a bit after it became clear that the villain was a computer. But the film is so predictable that there wasn't anything even interesting to keep my attention, and so it got to the point where I just couldn't wait for it to end. To the film's credit, it at least didn't drag things out.

If you like movies where the antagonist is a computer, have at it. But if you're like me and such movies aren't your thing, skip this one. And remember, computers don't kill people, people kill people. Or something.

ColdFusion @ Adobe MAX 2008

Adobe MAX 2008 figures to be the best MAX ever. But did you know that there are a ton of great ColdFusion sessions on tap? I don't know specifics, but I know there are more sessions planned this year than in at least the recent past. So...hopefully you have heard only good things about Adobe MAX, but if you instead heard something about there not being enough ColdFusion content, put that thought to rest! But don't just take my word for it, check out the Adobe MAX 2008 North America Session Locator and see for yourself (as Charlie Arehart pointed out to me, it's important to notice that the tool includes a Product selection and by choosing "ColdFusion" you will see over 30 distinct sessions, not including repeats, pertaining to ColdFusion)! Then check out all the great information and register on the Adobe MAX 2008 North America website. Speaking of registration: for the best possible price, you need a special code--and I may be able to provide one; contact me for more information.

Unsupported ColdFusion Configurations

I guess you could say this is the unofficial thread on unofficial ColdFusion configurations. :)

But before we get to that, I need to make this statement: I recommend running ColdFusion in a supported configuration as specified here:

http://www.adobe.com/products/coldfusion/systemreqs

ANY deviation from these System Requirements is strictly at your own risk! Among the risks is a lack of support from Adobe--Adobe only supports configurations meeting the System Requirements!

Now, let me explain things a little further: the System Requirements information indicates tested and supported configurations for ColdFusion; it does not (at least necessarily) contain definitive information on what configurations will run ColdFusion. That is to say, there may well be configurations not listed that will run ColdFusion, but Adobe cannot and will not make any comments about these and again I must stress that, most importantly, Adobe will not support such configurations.

I hope the information I have just shared is enlightening in and of itself; I think it will be because I'm regularly asked questions on the subject, usually in the form of "will xxx work with ColdFusion." But for those questions to which I have to answer "it is not supported, but as to whether or not it will work, I cannot say" my hope here is that others will be able to share their experiences with these unsupported configurations. My intention is in no way to encourage the use of ColdFusion with unsupported configurations; my only desire is to help those who choose to use such configurations knowingly and with a full understanding the implications of using such configurations.

So...if you have a question about an unsupported ColdFusion configuration, ask away in a comment! If your experience has been that ColdFusion either does or does not work with a certain unsupported configuration, please note it in a comment! When commenting, please specify as much information as possible about your configuration, certainly including your version of ColdFusion.

Adobe eSeminars

One of my roles at Adobe is to present eSeminars (online seminars via Adobe Acrobat Connect) related to ColdFusion. Join me, won't you? I will be presenting the Adobe ColdFusion 8 eSeminar Series over the next couple of months; details can be found via this URL:

http://www.adobe.com/cfusion/event/index.cfm?event=detail&id=1345643

Speaking of eSeminars: you might also be interested in the Adobe Flex eSeminar Series for Developers; details can be found via this URL:

http://www.adobe.com/cfusion/event/index.cfm?event=detail&id=462539

Upgrading from ColdFusion MX to ColdFusion 8

Just as I am frequently asked about the process of migrating from ColdFusion 5 or older to ColdFusion 8, I am also regularly asked about the process of upgrading from ColdFusion MX (the versions variously known as ColdFusion MX, ColdFusion MX 6, ColdFusion MX 6.1, ColdFusion MX 7, ColdFusion MX 7.0.1, ColdFusion MX 7.0.2, ColdFusion 7, ColdFusion 7.0.1, and ColdFusion 7.0.2) to ColdFusion 8 (at the time of this posting, the current release of ColdFusion 8 is ColdFusion 8.0.2). And so here too I have compiled some helpful information:

First and foremost, to set things up: as noted in the following link, ColdFusion MX to ColdFusion 8 is a valid upgrade path (upgrading to ColdFusion 8 is supported for the 2 most recent previous major releases of ColdFusion):

You can use the ColdFusion Code Compatibility Analyzer to determine if your code is valid for ColdFusion 8:

I recommend reviewing the tag and function changes to ColdFusion. Be sure to note the addition of functions with names that collide with user-defined functions in your code (for instance, ColdFusion 8 introduced the isImage() function; if your code has a user-defined function called isImage() you will need to change the name of that user-defined function and all references to it in your code before upgrading to ColdFusion 8):

You may also wish to check the CFML Language History:

It's very important to read the release notes in case some might apply to your environment:

Many of these upgrading best practices will certainly apply:

When you're ready to install ColdFusion 8, you'll want to review the "Installing and Using ColdFusion" documentation:

Adobe has worked hard to make the upgrade process as smooth and easy as possible. The process involved varies depending on:

  • Your current product version and edition as well as, in the case of ColdFusion Enterprise, your current deployment type.
  • Your desired product version and edition as well as, in the case of ColdFusion Enterprise, your desired deployment type.

To upgrade to ColdFusion 8 Enterprise from ColdFusion 8 Standard:

  • Enter your license key for ColdFusion 8 Enterprise in the ColdFusion Administrator in the System Information section accessible via the link marked with an "i" Information icon in the upper-right. No reinstall of ColdFusion 8 is required. This is true because there is a single runtime (per platform; the same is true for the installer) for ColdFusion 8 which acts as a particular edition based on what license key(s) are entered--if you enter a license key for ColdFusion 8 Enterprise, the runtime will act as ColdFusion 8 Enterprise; if you enter a license key for ColdFusion 8 Standard, the runtime will act as ColdFusion 8 Standard. Note that both ColdFusion 8 Trial and ColdFusion 8 Developer are the same as ColdFusion 8 Enterprise, with the notable exception that neither is licensed for production use, Trial becomes Developer after 30 days, and Developer accepts connections only from a limited number of IP addresses.

To upgrade to ColdFusion 8 from standalone installations of any release of ColdFusion MX (NOTE: the process is the same for both standalone installations of ColdFusion Enterprise and ColdFusion Standard):

  • Run the ColdFusion 8 installation wizard to install ColdFusion 8
  • Browse to the ColdFusion Administrator to launch the Configuration Wizard and allow it to import the settings from ColdFusion MX

To upgrade to ColdFusion 8 Enterprise from multi-server and J2EE installations of any release of ColdFusion MX, follow this TechNote:

As long as you choose to use the built-in web server during installation of ColdFusion 8, your installation of ColdFusion MX will not be altered or removed by the installation of ColdFusion 8. You will therefore be able to continue running ColdFusion MX while you test your new ColdFusion 8 installation.

If during installation of ColdFusion 8 you choose to use the same external web server as you are using for ColdFusion MX, note that the CFIDE and CFDOCS directories in the root of your external web server will be replaced by the CFIDE and CFDOCS directories for ColdFusion 8. If you wish to avoid this, you must instead choose to use the built-in web server during installation of ColdFusion 8. As Adobe Technical Account Manager Michael Collins explains in the following blog post, you can later use the Web Server Configuration Tool to configure your external web server for ColdFusion 8:

If you wish to configure your external web server to work properly with both ColdFusion MX and ColdFusion 8 on an ongoing basis (as opposed to working with only one version or the other), you can do so, but you will need to do some manual configuration of your web server; see the following blog post by Adobe Community Expert Charlie Arehart for more information (even if you're not using Microsoft IIS and Microsoft Windows XP, the principles described will apply):

There is no need for you to uninstall ColdFusion MX once you are no longer using it, but you may do so if you would like. However, if you wish to install any release of ColdFusion MX and you have ColdFusion configured to use an external web server, please view the following TechNote (which is written for the uninstallation of ColdFusion MX after upgrading to ColdFusion MX 7, but is also applicable to the uninstallation of any release of ColdFusion MX after upgrading to ColdFusion 8) before uninstalling ColdFusion MX:

Still have questions? First, visit the Installation section of the ColdFusion Support Center. If you can't find your answer there, feel free to contact me or, particularly if your question is one you believe would benefit other readers of this post, add a comment on this post.

One final note: Adobe offers implementation consulting for a fee; if you would like more information on this offering, please contact me.

Migrating from ColdFusion 5 or older to ColdFusion 8

I am regularly asked about the process of moving applications from ColdFusion 5 or older to ColdFusion 8. Nowhere else is there good consolidated information on the subject so, with some help from the excellent Adobe ColdFusion Support Team, I have compiled this information:

First and foremost, to set things up: as noted in the following link, ColdFusion 5 to ColdFusion 8 is not a valid upgrade path:

However, you can still migrate your ColdFusion applications from ColdFusion 5 to ColdFusion 8. Note that unlike the valid upgrade paths available for moving from ColdFusion MX 6.x and 7.x to ColdFusion 8, migrating from ColdFusion 5 to ColdFusion 8 does not allow for automated migration of ColdFusion settings like datasources, mappings, custom tag paths, and so on; instead, you must migrate your ColdFusion 5 settings to ColdFusion 8 manually.

Below you will find a number of resources that will be helpful in the process of migrating from ColdFusion 5 to ColdFusion 8:

This is probably one of the most valuable links that will cover many aspects of migrating from a previous release of ColdFusion to ColdFusion MX. Although this article was written for migration to ColdFusion MX, which is 2 full releases earlier than ColdFusion 8, many of the topics covered will apply to ColdFusion 8 as well:

The previous link also mentions the Code Compatibility Analyzer. You can use the ColdFusion Code Compatibility Analyzer to determine if your code is valid for ColdFusion 8:

I recommend also this link for ensuring your migration from ColdFusion 5 will at least be compatible with ColdFusion MX:

I recommend reviewing the tag and function changes to ColdFusion. Be sure to note the addition of functions with names that collide with user-defined functions in your code (for instance, ColdFusion 8 introduced the isImage() function; if your code has a user-defined function called isImage() you will need to change the name of that user-defined function and all references to it in your code before upgrading to ColdFusion 8):

You may also wish to check the CFML Language History:

It's very important to read the release notes in case some might apply to your environment:

Many of these upgrading best practices will certainly apply:

And finally, when you're ready to install ColdFusion 8, you'll want to review the "Installing and Using ColdFusion" documentation:

Still have questions? First, visit the Installation section of the ColdFusion Support Center. If you can't find your answer there, feel free to contact me or, particularly if your question is one you believe would benefit other readers of this post, add a comment on this post.

One final note: Adobe offers implementation consulting for a fee; if you would like more information on this offering, please contact me.

More Entries

BlogCFC was created by Raymond Camden. This blog is running version 5.9.002. Contact Blog Owner