How Are You Structuring Your Apps?

I'm curious as to how the average reader of these forums is architecting their ColdFusion applications. To expand on the poll options:

1. Ad-Hoc Page-Based: each user action is its own page that is called directly in the URL, i.e. listusers.cfm, adduser.cfm, deleteuser.cfm, etc.
2. Model-View-Controller / Framework: UI Controller framework such as Fusebox, Model-Glue, Mach-II, etc.
3. Model-View-Controller + Tiered Model Layers: UI Controller framework plus a tiered model including service layer, business object layer, data layer, etc.
4. Model-View-Controller + IOC Containers / ORM: UI Controller framework plus inversion of control containers like ColdSpring and/or object-relational mapping frameworks like Reactor

Please respond to the poll and comment here with your thoughts or approach on structuring an applicaiton. I'm interested to see how most folks are doing this and why.

Ad-Hoc Page-Based is much simpler to follow when a developer wishes to take over or work upon my project when I am not in the office. Other methods seem far too complex for no real benefit.

Ad-Hoc Page-Based is less complex but does not scale well to large applications and does not result in very maintainable applications. This would be akin to developing a Java application where all the code is in the main() method. Less complex? Probably. Scalable and maintainable? No.

I think my method is ad-hoc also but I devide it all up i keep my main global vars in the application.cfm page, use my index.cfm page just for the template stuff (wrapper of the content) include my content (cfinclude statement with pageid variable being called from the url) menu is included also as is the footer, basically all info that is generated or that remains static is included in the index.cfm template file, that allows me to change one part of the site from one file and not have to change a million of them. here is an example of what i mean with my newest CMS, http://v2.getmanaging.com it has 3 different sites (home, fm, cm) but yet they all use the same source files (same menu, content etc) but different index.cfm files where i change the layout and 2 variables that controll the include path of files and what content is displayed on the sites.

Yes, encapsulating the business logic from the display code is absolutely essential. When done properly, the same domain model can supply data to numerous views (not just separate sites, but web services, AJAX calls, Flash/Flex remoting calls, etc.).

I just started on a project here in the north-east and the way I'll be structuring the app would I think fall under ad-hoc page based architecture. All the globals are defined in application.cfm and like a previous poster described, the index.cfm is used more or less as a wrapper.

Is there a resource where I can read up on the pros and cons of all these architectures? thnx.

i hv a relational database which involves me recording the availabilaty of holiday houses and also taking bookings from customers. What data needs to be stored in which tables and fields for me to achieve this!so that i can also search the data base for houses available at particular weeks?please help!

you can also contact me @

(E-Mail address blocked: See forum rules)

thanks!

Elliot

If you have a specific question I'm happy to try to help, but if you're asking me to architect your application for you I'm afraid the answer will be no.

In my early days of CF before I learned the oop approach to coding cf I would do something I found very useful. I would create my own version of a fusebox but very list. I would have a directory called queries, and a directory called modules. And using a switch case statement in the application file I would decided which queries and modules were needed for each page. For example I would create a page called index.cfm index.cfm would have the main design of the site then based on the switch case in the application file the content section of the page would be filled in. I would use url params for what page I was on like index.cfm?page=about this was a fairly easy way to start seperating logic from presentation and let you learn a little deep cf coding. Try adding things to your case statement to chage the page titles of each page, and track user viewing stats. It will give you a bit more of the fundementals of a structured development project. Now I personally use model-glue as I love the RAD i get from using it. But be creative and try to come up with your own way of seperating logic from presentation. It will help you learn in the long run. But trust me cfc's are the way to go. AD-HOC is not very developer friendly.

There really is no central resource that I am aware of, but a simple search for any of these will provide numerous results. There are also mailing lists available for all of these (Fusebox, Mach-II, Model-Glue, Reactor, ColdSpring, and others). Hope that helps!

Since picking up Fusebox I'll never go back to ad-hoc.

The ability for anyone to look at my app, know exactly where everything is and how it is managed is by far the greatest positive.

I will be beginning to pick up Mach-ii and I am very excited to start programing in OO.

I have build site using Fusebox, and enjoyed it.. but now doing it adhoc as i cant remember the logic i plan (due to short term memory loss, after an accident). I did using Fusebox to build an online pharmacy, a banner management system and an online lottery, but it was quiet a few years ago..
Will probably go back to fusebox if my memory allows it..

I use CF for all my database admin stuff. Not sure which method I'm using, though. Maybe ad-hoc? I have a folder for each database table and within each folder are do.cfm and form.cfm scripts. The "form" script renders the form to add or edit entries and the "do" script does all the database stuff.

No wonder CF'ers get no respect.


I use a MVC framwork like Mach II for the most stuff and depending on the scale of the project, I will use a service layer, business object layer and ORM. But even for quick and dirty "add hoc" stuff I will use cfcgenerator to generate my data layer (bean, gateway, DAO) just to not have to rewrite all my queries if I need to make changes to the database structure (Which I most likely will). That way if I add a field to the database I don't have to add it to and insert, updated and select queries. I just re-generate the CFC's. 9 times out of 10 all I need to do is add the new databse field to a form and/or a view page. I suppose I could use ORM but that would be over kill for simple stuff.

I use cfcgenerator btw http://code.google.com/p/cfcgenerator/

And all I need to do to snag data from the data base I just add 2 lines of code.




And then I can use a generic controller to handle my CRUD functions. With this all I need to do is swap out the name of the table I am using. For this I am using "hrlinks". To change it to "hrdocs" I do a simple search and replace for that string and I have a basic CRUD app with out writing a line of code.