> I've often wondered about this is there really a need for > a third tier, what would you put in the third tier that you > *couldn't* put in a stored proc apart from file operations?
Well, given the fact that the vast majority of client-server and web applications are two-tier, you could make the argument that in most cases, there's no need for a third tier. However, in some applications, there's a definite need. Consider applications that use multiple databases, or that want to apply transactional logic across a scope greater than one database. A middle tier makes that quite a bit easier. Also, even when there isn't a need, you can make the argument that there are advantages to using a middle tier - it allows you to have a place for logic which isn't strictly data-manipulation logic (the kind of stuff you'd put in SPs) but which isn't presentation logic (things like HTML output formatting) either. This vague category of logic is often referred to as "business logic", but in reality business logic may spill over into other tiers as well, of course. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ______________________________________________________________________ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
