Français, English

N-Tiered Architecture and Thin Client

>Does N-tiers architecture mean Thin Client? 

Answer is certainly Yes. As one of the goal of a n-tiered architecture is to separate the whole system into specialized layers (layers and tiers are synonyms), the upper tier should be totally dedicated to the GUI (Graphical user Interface). In fact the UI in many business application is itself made of a set of tiers including UI and Presentation. For instance a typical UI tiers set in a Web-based application is made of some C# classes (tier #1) that generates the DHTML/JScript (tuers #2) code to be displayed into the Browser .

Nevertheless there are some cases where a the user experience a thin client can provide is not reach enough. In those situations the thickness of the client shall not be blocking. For instance an IDE application (Integrated Development Environment) could not be put up with a Ultra Thin Client like Internet Explorer.

>Does Thin Client mean an Internet Browser like IE?

N-tier archictecured applications are already always associated with an Internet Browser Thin Client. There are many reasons for that: N-tiered application are truly possible because of the growth of the Internet and the huge set of technologies and tools it makes available to the software developpers. Among these tools the Internet Browser is; and more it is suitable for many application. Also every PC's comes up with an Internet Explorer installed so the client upper tier deployment is considerably simplified (but still exist).

Unfortunately IE or any other Web Browser is far to be suitable for all kind of applications. For instance could you seriously think to replace your current General Ledger package, probably working with a Terminal emulation or a not thin client by Web Browser UI? What would happen when an accountant missing a data entry because he would have lost the "page" he was working on after he ill-advisedly . Visit our Yke© Page 

 

>Is there any Thin Client Alternative to WebBrowser ?

In an ideal world the solution would be to use IE without IE. Actually that what we propose in many situations, so the end-user exeperience wealth would be preserved. IE without IE means the application uses 90% of IE code, already present on the user PC, plus a light programm which acts as a the container for GUI tier. This tool is   Yke ©.  More about Yke ©