To take away your con, we use SES urls (search engine safe). Erik V made a tag that changes a url from index.cfm?fuseaciont=something.something&here=there to index.cfm/fuseaction/something.something/here/there/index.html . Not only will this help with the crappy search engines that aren't google, it will make your reporting accurate.
Robert Everland III Dixon Ticonderoga Web Developer Extraordinaire -----Original Message----- From: Donny Ng [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 12, 2002 10:27 AM To: CF-Talk Subject: RE: Fusebox pros and cons Very well said. One more Pro: - It also faclitate developers to work in team. e.g. I will take care of the "login" circuit and you will take care of the "ShoppingCart" circuit. Yet one more Con: - FB is nasty if your clients need reporting on their website. Since FB always goes thru index.cfm first. You might get millions of hits to index.cfm but 0 hits to the other files. I suppose reporting is possible, just need some extra work. Just my 2 cents Donny iLogic Inc. -----Original Message----- From: James Maltby [mailto:[EMAIL PROTECTED]] Sent: March 12, 2002 7:14 AM To: CF-Talk Subject: RE: Fusebox pros and cons Can open, worms all over the floor! IMHO - Fusebox is a methodology with a lot of dedicated followers - if you come to CF from a "coders" background it's very rare for you to adopt fusebox (unless you are first taught this way), however if you come to CF from a "programmers" background you will take to fusebox like a java built duck to object oriented water. Advantages: 1) re-use your code (build something once, then plug it in again and again to each of your solutions) - reuse code in a O-O style. 2) work by piece rate (farm out whole sections of your product and have people in sweat shops work over "fuses" for you while never being able to see the whole picture) - remote and rapid component development 3) build the bricks first then make rooms then slot the rooms together (build a site completely before you even put it together) - rapid component development and site building. Disadvantages: 1) Non-linear development structure (hard to get your head around if you build sites "organically" from seed to flower - fusebox seems like DNA level work - where you can build the flower first then get around to the seed.) 2) Needs very good documentation to follow (very hard to "fix" an error in a site if you weren't responsible for boxing all the fuses - really depends on how well the site was built along the fb guidelines) 3) Hard to re-train if you're not a programmer - we've got 8 CF developers world-wide working for us and only two of them use FB - both of these come from hard-core programming backgrounds, others have tried and given up - FB is a lifestyle choice and not just for Christmas! Hal Helms is the daddy, anything written by him is groovy - but I think there may be two FB camps now.... J -----Original Message----- From: Thane Sherrington [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 12, 2002 11:51 To: CF-Talk Subject: Fusebox pros and cons I've never used fusebox, so I'm wondering if it is worth taking the time to learn. What are the advantages or disadvantages to it? Are there any good books/webpages on learning it? What additional stuff do I need on my server to be able to use it? Thanks, T ______________________________________________________________________ Get Your Own Dedicated Windows 2000 Server PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER Instant Activation · $99/Month · Free Setup http://www.pennyhost.com/redirect.cfm?adcode=coldfusionb FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
