I would say, I can see some benefits right out there when using "Hub and Spoke 
Architecture" or similar Architectural Framework.
Code Clarity and Conciseness, hence Readibility
Benefits: for application debugging, team collaboration, maintenance, future 
functional enhancements, presentation modification etc. etc.

The alternative is spagette (shoot, how to spell it?) code, which everyone avoids.

One possible disadvantage of the above architecture is, heavy simultaneous requests 
handling by server, but there may be technique to circumvent that short-coming.

An ironic episode, a few weeks ago, one guys sent me a huge zipped file for some data 
admin feature using FuseBox (I don't recall which version), when I ran it, it took 
forever to execute a basic request, I guess he could be the slowest learner in using 
FB.  Then, I don't bother to look at his codes, instead, I wrote what it is now, 
SureFire, which is a re-usable, repeatable solution, 
http://68.32.61.40/datadata/DataMan.cfm


Li, Chunshen (Don)




>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.
>However, my original question was not specific to Fusebox but to the
>benefits of one design feature of Fusebox (and other frameworks),
>specifically, use of the Hub and Spoke Architecture.  So, here's a new
>thread for the original (and now rewritten) question...
>
>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?
>
>The most recognizable example of this model, in the CF community, is Fusebox
>in which all requests go to /index.cfm and specific files are executed based
>on the value of the fuseaction URL variable (i.e.,
>"index.cfm?fuseaction=cart.addItem&itemID=123").  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")?
>
>Another example of this would be along the lines of
>"index.cfm?displayPage=5" as opposed to "page5.cfm" (preferably with a more
>descriptive filename).
>
>Again, I'm not really asking about XFAs, APIs, etc. unless they are a direct
>result of going through the application spine.  Specifically, I'm asking
>about why people prefer to go through an application spine or why they
>prefer not to.  Benefits and downsides.  Pros and cons.  Too much typing...
>Thanks.
>
>--
>Mosh Teitelbaum
>evoch, LLC
>Tel: (301) 942-5378
>Fax: (301) 933-3651
>Email: [EMAIL PROTECTED]
>WWW: http://www.evoch.com/
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
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

This list and all House of Fusion resources hosted by CFHosting.com. The place for 
dependable ColdFusion Hosting.
http://www.cfhosting.com

                                Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
                                

Reply via email to