Wrox Programmer Forums
.NET Framework 1.x For discussing versions 1.0 and 1.1 of the Microsoft .NET Framework.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the .NET Framework 1.x section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
Old October 19th, 2006, 12:05 PM
Registered User
Join Date: Oct 2006
Posts: 6
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via Yahoo to rajdotnet
Default 3-tier architect

Hi, I read wrox book asp.net 1.1 in that author says
in fig 13.1

a html->application logic->database

is three tier architecture. how it can be a 3-tier

for this we need presentation layer()html->application logic->data-logic -> DATABASE

plz clarify

Old November 3rd, 2006, 03:59 PM
Registered User
Join Date: Oct 2006
Posts: 4
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via Yahoo to srikant_jan

Three tier contains a presentation layer that is true which is html second it consits of business layer which is application logic and thrid the database which is data base which goes as above
html->application logic->database

Janamanchi Shrikanth Narsinha Ramulu
Old November 3rd, 2006, 07:01 PM
Friend of Wrox
Join Date: May 2006
Posts: 643
Thanks: 0
Thanked 0 Times in 0 Posts

Conceptually, either of the scenarios could be considered "3-tier" - from a logical perspective data-logic/database could easily be considered the "same tier". This is a fine point that shouldn't be of concern.

In a dynamiclly generated web app (also sometimes called a data-driven site) it is often discussed as having another conceptual "tier":
Browser -> Web Presentation -> Business/Application Logic -> Data store.

Browser: contains some logic for validations and accepts user input
Web Presentation: Dynamically generates the HTML, and handles user requests
Business Logic: Does the work of the application.
Data store: Persists and retrieves data as required by the business logic.

I suggest that this isn't an area where it matters much exactly how you call things - the basic idea is that the logic is divided into various tiers that are best suited to handling the logic needed.

Woody Z http://www.learntoprogramnow.com

Similar Threads
Thread Thread Starter Forum Replies Last Post
Difference between 3 tier and N-Tier architecture Manoj Bisht ASP.NET 2.0 Professional 2 May 9th, 2008 08:42 AM
3 Tier example fj8283888 Pro VB.NET 2002/2003 1 August 2nd, 2006 03:44 AM
For n-tier application Ned XML 4 July 27th, 2005 04:54 AM
j2ee architect sample papers?? rahulsaxena J2EE 1 September 28th, 2004 01:53 AM

Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.