Migrating to Application cfc

This is not a question about the structure of an Application.cfc, I've got that down. No problem. This is about taking a bunch of apps that use the same application scope but different Application.cfm files, and converting them one by one to Application.cfc. All of these have the same Application scope of "MyApp" so the user only has to log into one app, and they are thus logged into them all. tools/calc/Application.cfm tools/time/Application.cfm apps/funstuff/Application.cfm Now, my question is...what happens if I change one those to use Application.cfc and leave the others at Application.cfm. Am I asking for a world of hurt and hidden consequences? or will everything play nicely together. I would still have to worry about values being overwritten and other enjoyable bugs like that. :) Thanks in advance.

This question has been tossed around a few lists lately. I have not verified, but from what I understand as long as you have the same application name within the application.cfc and application.cfm files, then you should be ok. On Thu, Apr 10, 2008 at 9:38 AM, Jeff Price <houseoffusion@ijeff.com> wrote: ----- Excess quoted text cut - see Original Post for more -----

As long as you use the same application name, the application has no awareness of an Application.cfm/cfc distinction.  Only the Application.* file itself is different. Both have strengths and weaknesses. cheers, barneyb On Thu, Apr 10, 2008 at 9:38 AM, Jeff Price <houseoffusion@ijeff.com> wrote: ----- Excess quoted text cut - see Original Post for more ----- -- Barney Boisvert bboisvert@gmail.com http://www.barneyb.com/ Got Gmail? I have 100 invites.

Barney, I would be interested in knowing what are the weaknesses in Application.cfc based on your expertise. Thanks On Thu, Apr 10, 2008 at 12:47 PM, Barney Boisvert <bboisvert@gmail.com> wrote: ----- Excess quoted text cut - see Original Post for more -----

The primary one is that you can't set variables in the page's variables scope without using onRequest, which breaks remote calls. You can use the request scope from onRequestStart, of course, but there are different semantics for that (like being shared across CFCs/custom tags).  Less troubling, but still annoying, is that the property names used to configure the application are not enforced at all, so a typo there can be very difficult to track down. Of course, with Application.cfm you can't have per-application mappings or session events and you have to manage your application startup manually, but I do the last with Application.cfc so I don't have to cycle CF all the time. cheers, barneyb On Thu, Apr 10, 2008 at 10:50 AM, Qasim Rasheed <qasim.lists@gmail.com> wrote: ----- Excess quoted text cut - see Original Post for more -----

>The primary one is that you can't set variables in the page's >variables scope without using onRequest, which breaks remote calls. >You can use the request scope from onRequestStart, of course, but >there are different semantics for that (like being shared across >CFCs/custom tags).  Less troubling, but still annoying, is that the >property names used to configure the application are not enforced at >all, so a typo there can be very difficult to track down. Out of curiosity, is this thing by design or an oversight?  Thks.

Thanks Patrick and Barney! This list rocks :) -jeff >As long as you use the same application name, the application has no >awareness of an Application.cfm/cfc distinction.  Only the >Application.* file itself is different. Both have strengths and >weaknesses.