On Thursday, Jul 17, 2003, at 13:08 US/Pacific, Mosh Teitelbaum wrote:
> First, thanks to Brian for the dialogue concerning the pros and cons of
> Fusebox. I intend to keep at that line of conversation in the thread.
It's an interesting thread.
>> From your own experiences and your own thoughts on the subject, what
>> are the
> benefits and downsides to designing a site (whether by way of a
> framework or
> otherwise) in which all requests must go through a single file which
> then
> redirects or includes other files to handle the specific needs of the
> current request?
Benefits:
- abstraction of URL structure from file system
- allows you to reorganize and refactor code without breaking /
changing links
- provides a central place for requests
- you can add standardized layouts
- you can hook in security or other filters
Downsides:
- abstractions always create some performance overhead
- developers new to the project have to learn the mapping
> How is this better or
> worse than an architecture in which the same action would go directly
> to the
> "addItem.cfm" file (i.e., "/Cart/addItem.cfm?itemID=123")?
You can't refactor the code without breaking the site API (the URLs)...
unless you leave a bunch of redirects in place.
(probably a lot more stuff but that's off the top of my head)
Sean A Corfield -- http://www.corfield.org/blog/
"If you're not annoying somebody, you're not really alive."
-- Margaret Atwood
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription:
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Get the mailserver that powers this list at
http://www.coolfusion.com
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
