The British changed the world right, that is, the friend changed the whole world inadvertently. During the work of Cern (EUROPEAN Particle Physics Laborative, the European Quantum Physics Research Institute), CERN has discovered the shortcomings of information in the internal communication of information, so in March 1989 TIM submitted to Cern "Information Management: A Proposal's Recommendation, this is also the first public document on the Internet concept so far. In this document, TIM proposes to use Hypertext to construct a link information system. Similarly, we can also see the initial proposal of "Browser" concept from the file. In 1991, on this basis, TIM has developed the first true web server - httpd, the first client browser --worldwideweb, and then established and opened in 1991 and opened the first WWW website http: / /info.cern.ch/ (The site is still the official site of Cern). Since then, the Internet really begins to popularize society. As for later TIM Join MIT LSC (Computer Science Laboratory) and later established W3C and another far-reaching thing. Anyway, through WWW, this a bit honest British has completely changed the whole world. In May 1993, the genius of the University of Illinois developed the first browser MOSAIC. In the first half of 1994, he and Jim Clark have set up Mosaic Communications (the predecessor of Netscape), which released Netscape in October in the same year. 0.9, this is the first browser of the first browser we see, although today is already unrecognizable. The emergence of Netscape has finally made WWW get an explosive popularity. Browser / Server, an unable to be a perfect name With the beginning of the browser war, the world's true sense of enjoyment of scientific and technological progress to human beings. One night, the B / S structure has become the most mainstream architecture of application development, and the browser has a unique tool for the client. This software application that does not require deployment does give a lot of people unlimited. ISV, solution providers and their business users have also proposed to adopt B / S architecture as an architecture of enterprise information applications, because it can be exempt from high deployment and upgrade fees before C / S age, and can quickly adapt to constant changing companies. business. Gradually, they found that their constant business through simple page browsing has not met the requirements, this time related client script is going to the stage, saying a bit dramatic, the original intention of Netscape design scripts is to make the webpage better Browsing, thereby increasing the fun of page browsing, they must not think that this concept is on their opponents, waiting until the smoke of the browser war, we found that the script has faced unrecognizable, or it has been bloated . In order to follow the interface experience under the C / S structure, developers have to use a large number of JavaScript and DHTML to implement or say "simulation" interface interface, such as menus, toolbars, and complex graphics and forms. . Because of this, Web has become the most popular application field today. In addition to related server development technologies such as ASP, PHP, JSP has later kings ASP.NET, client technology includes HTML, CSS, JavaScript, DHTML, etc. Aspects of technologies, have become a chase of developers. What is even more, using client technology to develop a complete set of complete class libraries, this is the most famous of Bindows (you can download from http://www.bindows.net).
After solving the problem of deploying and updating, B / S also introduces some headache problems: 1) There is no very standard technical specification to agree, resulting in extensions made outside W3C. In application development, more is to rely on these extensions to achieve more beautiful graphical performance and flexible interaction. For example, IE proposes the concept of HTC, and has added a number of related filters, and Mozilla also proposes XUL to extend the user interface. But if you need to design a powerful user system, we have to rely on the extension implementation of the proprietary browser. 2) As a browser war IE has not launched an important version update after 2001, then all of our development technology is the concept of stagnation before 2001, this and server-side technology is constantly evolving It has gradually been gradually detached. 3) As a browser-based application, because of security, etc., the reason that can be used to become applications can be done, more time is passive to accept the application provided by a single server, such as the client hopes to cross different networks. Call the relevant Web Services, because the deformed of the security model (not very complete resource access control), we cannot achieve cross-app integration throughout the same browser [1]. 4) Based on browser-based skills, it is based on online access. In the application of some offline lines, it seems that it is powerful, after all, from the beginning of the browser design, hope to be able to care The "sandbox" model of a minimum permissions is running, so the access to local resources is rejected by default, and some browsers such as IE allow for passing this security model, but does not provide a very good authority Layer mechanism, the gate opened, everything is like a flood beast. Browser / Server, this scene of scenery in the past 10 years is still not so good. What do we need? In fact, the reasons are already very simple. Although many C / S or Rich Client regression have appeared on the Internet, I think more is because of the problems currently existing in the B / S architecture, because in essence, many problems It does not exist in the C / S structure. Anyway, I want to return to just a tendency, I hope to use the advantages of C / S to solve all kinds of problems in B / S, rather than simple return, if this is true, we have to repeat the past disaster is like The deployment of headache, frequent upgrades, the version compatible problem, I want to repeat the same mistakes for the company's IT workers. So what do we need? TIM has changed this world through the Internet, then what will the next step will be going? At this time, the argument of RIA (RICH Internet Application) is also formed and recognized by developers and system architects in 2004. In a strict sense, we will not care which name abbreviation will be the mainstream of the next generation, and we are more focused on the technology that needs to be resolved. 1) Need a more powerful client operating environment while providing a unified simple development model. In a sense, the current browser is the runtime of HTML and scripts. All code (HTML, CSS, JavaScript), etc. are running in the browser's controlled environment. But the current operating environment is far less, without a unified programming model.
2) Extensive use of client resources, and resource access is completed in a controlled environment, with HTML and CSS evolution, no longer starting a HyperLink (super connection) is then simple, but relative Windows running environment, graphic performance that can be completed on your browser is far less enough. 3) The ability to access the network while comparing the application of "smart" integrated Internet. 4) Automatically complete security and upgrade 5) Have a complete security model and CAS (code access security). 6) The ability to offline applications, because the access to the terminal is diversified, support for "time offline" has become a key point, for example, when the application based on a smartphone is required, it is required to be a bit of difficult, this time is in mobile. The traditional B / S structure in the application is not realistic. For the above requirements, some mainstream application vendors have also proposed their different concepts, such as Microsoft's Smart Client technology, Macromedia's Rich Client and Mozilla's XUL, which is the three mainstream RIA application architectures. Do some elaboration. The mainstream RIA application architecture Microsoft Smart Client From a sense, Microsoft's smart client and the above mentioned mentioned are the most close, and it also provides the most complete operational environment support. Intelligent clients differ in design and implementation, including both application requirements, including their solutions and environments. Therefore, smart clients can take many different forms and styles. According to the platform facing the intelligent client application, these forms can be divided into three categories: 1) Windows smart client application Windows smart client applications are suitable for deploying applications as familiar desktop type applications. And access. These types of applications typically provide most of their functions, but can integrate or coordinate other applications when appropriate. They provide applications for specific tasks to provide specific or high performance processing or graphics capabilities. 2) Office Smart Client Applications Microsoft Office System 2003 provides you with a useful platform for generating smart client applications (especially in business settings). Such Office Smart Client Applications can be an integral part of the organization's information management cycle, not just a static container for document data. When the user operates within the document, they can provide context-related data, and convert data disclosed in Web services to workflow and task guidance, data analysis, collaboration, reporting, and presentation functions. 3) Mobile Intelligent Client Application Mobile Intelligent Client is an application running on a smart device that includes Pocket PC, Smartphone, and other ultra-small desktop devices (such as set-top boxes). These applications are developed using the .NET framework compression version (which is a complete .NET framework). Speaking of this, we have to mention .NET, is this unified programming model to make Smart Client possible, from a sense, .NET Framework has the so-called needs of the above mentioned above, including Internet access capabilities, including Web Services Access, including CAS, including powerful WinForm, etc., and related Application Blocks available on the MSDN site can speed up the pace of these applications.
Before Longhorn's Avalon did not arrive, .NET's implementation of some Rich Client should be the most complete, although Java also proposed the concept of WebStart, but we know that Java does not have too great advantage in the desktop application field, including the earliest Applet, later SWT and SWING, etc., unless you need to cross the platform applications, Java doesn't have much advantage in the desktop application field. If the .NET Framework has already made a home for Ria, then Visual Studio.net is the tool that its implemented, as the best IDE, the SMART Client also provides built-in support. For developers, you can use VS.NET to easily build your own application. Macromedia Flex relative to Microsoft's Smart Client, the Boss Macromedia as an Internet Multimedia Application also proposes the concept of Rich Client, and the opposite of .NET, not to provide a powerful operating environment, but put all the applications in Flash On, after all, 99% of browsers around the world will have a flash player. Flex is more focused on the implementation of the UI, completing the ActionScript in interaction, and built-in technology provides Web Services access, XML applications, etc. A little similar to Longhorn Avalon, proposing a more powerful UI description language relative to HTML to make developers more convenient to apply development, and provide a large performance capability by built-in components and scripts (ActionScript). Don't think that ActionScript is simple JavaScript, in addition to the full implementation of ECMA 262 EDTION 3 specification, simultaneous joining many of its own extensions, the name of the action script has been named, objectively, is already a powerful language. In terms of graphics, Flex's application is worse than smart client, but it is far less than .NET support than smart client. Although Flex is strong enough, its expensive software license does not limit the development of a special smooth development environment, and Flex has to be a mainstream and need some time. Mozilla XUL XUL's core idea is "Expressing the interface with XML", is the innovation of Mozilla, the Mozilla browser itself is a classic XUL application. As the successor of Netscape, Mozilla becomes some techniciary, the most recent Firefox is a bit unexpected to get more people's recognition. From a direct feeling, XUL is a framework for a client operating environment support, providing more support relative to HTML, XUL, and the behavior of IE5 is a bit close. But XUL provides a more flexible model than HTC, and because Mozilla itself is designed to run in different operating systems, therefore is better from this perspective. But because IE occupies an absolute mainstream, XUL is more only an experimental concept. Everything is already clear. I firmly believe that RIA will replace many browser-based applications in the past few years. This does not mean that the conversion does not bring any pain to them. It requires developers to learn new distributed architecture and new technologies. In many cases, they must better carry out object-oriented development and user interface design. Those developers who spend more than five years can do not want to make changes based on browser deployment. They are accustomed to the leading developers as their era.
However, all technologies will experience Ding Sheng, decline, and finally updated technology. Although we will continue to see a browser-based application will still use many years in some cases, but I believe that the browser-based development is now overded. It may be a period of time from the top to decline, but this direction is clear. Ready to welcome RIA's arrival! [1] Playing a simple alteration, the remote site A provides the weather forecast service, the site B provides a schedule management service, the site c provides some travel-related web services, this time if the integrator needs three sites, These services are required to be integrated in the server, and then available to the client through a predetermined manner, more portalet (Java terminology) or Web Parts (Technical) provided in customization. But it is impossible to do the customer's own integration. Azure's supplement: "RIA will replace many browser-based applications in the future", Ria itself can also be a browser-based application, and now more RIA is based on The browser, the browser gave people a door that is convenient to enter the network world. The emergence of new technologies has made a branch of the network application. Based on the browser RICH Client runtime (or the browser itself comes with the RICH Client runtime) application for a long time exists; Browser applications will be more and more.
