> Code Clarity and Conciseness, hence Readibility How does this design improve code clarity and conciseness over that of other designs? Can you give me some examples?
> Benefits: for application debugging, team collaboration, > maintenance, future functional enhancements, presentation > modification etc. etc. Again, can you provide some specific examples? > The alternative is spagette (shoot, how to spell it?) code, which > everyone avoids. Hub and Spoke does not protect against spaghetti code. Nor do other designs lend themselves to spaghetti code. That's more a function of the individual architect/developer. I've seen plenty of poorly written code using H&S and have also seen plenty of sparkling code using other designs. > One possible disadvantage of the above architecture is, heavy > simultaneous requests handling by server, but there may be > technique to circumvent that short-coming. Actually, the overhead of going through a single application spine is pretty insignificant. However, if the spine were to perform unnecessary processing before every request than it likely would hurt performance. However, the same could be said for having the same unnecessary processing in the Application.cfm or at the top of every file, so this is not a problem that is inherent in H&S. -- 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 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
