Thanks andw928. I should have said that I posted a similar question about 2 months ago about which method to use, so I have definitely settled on Fusebox.
This is a single operation, so the group requirement probably won't be there.
I was concerned about the web logging results, a conundrum. I believe as long as proper documentation is used, the file naming into function roles wouldn't be too difficult to manage. I posted a similar question a while ago about which one to use, and got some input that you can use whatever convention you want .
The last point, crippling the search engines is my primary concern. At the most I would have 2 url parameters, but the page parameter could be up to 3 words long with dashes (or underscores?). I just don't know how google handles content all being from one page, well, google and the others.
I do like the organization and reusability of fusebox. I like that it can be ported easily and that java is a snap to integrate. I also like that it will force me to stop writing spaghetti code! It's nice to have to write a query one time and keep it one place, combined with cfcs, 4.1 seems to be really powerful. I hope it isn't too difficult to debug!
Main Topics
Browse All Topics





by: andw928Posted on 2005-08-23 at 07:37:25ID: 14733916
Like all develoment methodologies, fusebox takes a bit to adapt to. I mean you have to be familiar with the whole structure and how the application functions before you develop the application, since fusebox is used to code a page a particular way, while others may be used to different ways which they think it is better.
The whole point of using fusebox, and developement methodologies, and CVS is to organize the work when working with groups. I never use a single methodology when working alone, there's no reason to.
Some people think fusebox applications aren't as portable and that they have a little bit "too much overhead". It is also sometimes harder to debug fusebox applications than it is to debug a regular template.
Other bad things about it are server software logging tools, that log visitors, these softwares will usually log all visitors under index.cfm, since it is all included from that 1 single file.
Also, fusebox's file naming convention is based on "files' technical roles in the application" rather than their "functional roles".
Finally, if you are using fusebox, that is even more crippling for search engines, as now not only do they see long url query strings, but also see all the content on 1 index.cfm page. You have to be careful with this as well.
Some of these quotes are from Web Application Construction Kit book by Ben Forta, from Chapter 37 on Developement Methodologies, and some of them are mine. So goodluck building your application whatever you choose to use!