Who is this article? Programming for beginners or those who ask the question what this gibberish about thin clients, heavy or I do not know what ...
IT is constantly evolving practices arising too. Yesterday the computer did not pass by the command line, then appeared the first graphical user interfaces that have magnified the potential of the computer tool. Are apparuent with new uses of this tool the concepts of ergonomics and aesthetics. Concepts on which I will not. Indeed for this post I'm going to address the functional side of IT. During the design of an IT project several notions recur frequently. The technologies employed, languages, and infrastructures. It is on this latter notion that I will focus.
There are 3 types of infrastructure, customers said "Heavy" which are software services running on all the post customer. Customers 'Rich' who are running them on the client but which part of the operation was deported on a remote server. And finally customers "Light" which are themselves entirely on the remote server, the interface is not stored on the client and rendering application is generated based on data sent by the server.
Briefly, the 3 major Possible types of infrastructure. So for my application, what infrastructure do I need? As you can see, there is no infrastructure outperforming others. All is a matter of needs, and these needs we will study in detail.
Customer Heavy
If your application does not require connection to a remote server, is that a priori it is sufficient in itself. Contrary to your feed reader application does not require frequent updating. In this case Customer Heavy is ideal. Heavy with the client you will have the advantage of being able to apply it better integrated with the OS, provided you choose the right framework. Often you must choose between portability and system integration / performance. Native applications take better advantage of the computing power of the machine. What does this mean? If your application requires significant computing power, to read or encode a video for example, or display of 3D models, you will turn instead to the libraries of your OS . The language most used in this case is C / C + +. If you power matter, and the portability of your application is paramount in this case it will be JAVA to you direct, though the couple Qt / C + + is also an interesting solution.
|
| Autodesk Maya, developed in Qt / C + + |
If your application requires connection to a server, to display content online data bank accounts, or any other action that requires information to be centralized on servers. In this case 2 choices to you: The Rich Client and Thin Client.
The Rich Client
The Rich Client is actually a fat client, which is to graft capacity to connect, to search for information on a network. This allows one hand to make the display dynamic information, but also, in some cases to reduce the processing done on the client. In fact, the server can perform treatments in place of the client. In the data processing for example, will tend to deport calculations on the server and send only the result to the client. The infrastructure for the benefit of pushing the hardware obsolescence of client machines, given that they require less power, while maintaining a consistent look and feel with the operating system of the machine. Furthermore it still allows to ask the client to perform heavy computations, such as 3D rendering, or animation. Rich client needed so when you have a need for connectivity and power and that it wants to store data on the client.
|
| Reeder mac |
The Thin Client
Finally when the Thin Client to him has the extreme advantage (for the designer and maintainer) do not store on the client. Specifically what benefits it brings on? simply in the question of updates from the application that is a huge advantage. Indeed, the update is done seamlessly, since the interface is downloaded from the server to each launch. The workstation is therefore needed when you have the need to frequently update application, both in its substance and in form. The disadvantage of this solution is that for the time components of the application does not provide the same reports as native components of the client. At least one is limited to the ability or web frameworks RIA. Most often, the application is isolated in a browser window, but some solution, like Adobe Air can get a standalone browser and more or less "disguised" as a native application.
Many frameworks exist for the thin client, I will not mention that GWT (Google Web Toolkit allows to create interfaces in HTML coding renduent JAVA) and Adobe Flex (Misuse of Flash technology to interface with online integration of video and animations that HTML does not). Because the thin client has no access to client data for security (the so-called "sandbox"), it is not possible to directly store or read information locally. All was deported on the server. It exists because Air a means to bring applications built with web technologies on the client. We can push the limits of thin clients by storing it locally, but ultimately we lose the interest of the thin client to return to the rich client. Finally you are left with the option of going through the traditional method, ie the HTML + CSS + JavaScript, which also allows you to create applications (admittedly smaller, since the type of code does not allow a good maintenance on large projects), like a website.
|
| Application made with Ext-GWT |
To make the point here is a very vivid graphics of Camille Roux to do review the various technologies for interfaces along the axis that we discussed.
I hope that this post will end you lit lanterns. I think in a future more or less certain look into the creation of an article or I will detail the various technologies for each infrastructure. Feel free to leave your opinion if you think I am miserably Gouré a point ^ ^ Bonne continuation.
0 comments:
Post a Comment