New thinking of enterprise application development based on Java-EE architecture: Who is the Web application centered? Browser? Server
Enterprise Web application, refers to the enterprise internal use B/s framework to build enterprise information system, the user is generally limited within the enterprise, in order to adapt to a business process design and development use of the system.
For cross-regional deployment upgrades, the B/S model is generally used to develop, to avoid the trouble of installing configuration on each client.
In general, the foreground browser refers specifically to IE, and the foreground operating system chooses the Windows operating system.
Non-Windows operating system clients and non-IE browsers are not covered in this article.
This article mainly discusses the Java-EE architecture based Web applications, other architectures are not discussed.
In this case, the data is stored on the database, generally not much doubt. The attachment file is generally stored on the Web server, there is no big doubt.
The main question is: Should the entire application be browser-centric or server-centric?
In the early days of Java-EE, this problem does not exist, then the browser, basically can be regarded as the Internet era terminals. The computing pattern at the time was based entirely on the backend server's calculations.
The historical development and evolution of 3.1B/S
Division of Computing Times |
Browser |
Server |
Summarize |
Times of prehistoric times/static pages |
Only HTML is supported, only text and pictures can be displayed |
static file storage; |
Static times, no dynamic content |
Prehistoric times/cgi Dynamic page era |
HTML only supported |
Dynamically generating an HTML file to the browser using a CGI method |
Dynamic times, dynamic information generated by the background server computing, not with the front desk |
Java Applet ActiveX Control era |
Browsers can embed other applications to display dynamic content JavaScript appears |
|
For the first time, the browser has the computing power to liberate computing resources from the server. |
The era of application server in Java EE era |
Applets are discarded and JavaScript begins to evolve |
Background using Java-EE architecture, JSP and other ways to generate dynamic pages |
The Java EE architecture binds the system's center of gravity firmly to the backend application server. |
Post-Java era Open source movement era |
JavaScript begins to grow, Ajax appears |
Java-EE began to decline, to make up for its flaws, open source framework appears. SSH is a great way to do it |
The application server is overwhelmed and the lightweight framework begins to appear as a substitute. |
The return of the King Ajax era |
Ajax rage JavaScript frameworks appear in large numbers. Flex/sl/extjs each line of the road |
Server-side stalled, JSF flash in the pan |
The background of the problem has been basically resolved, and now focus on turning to the front desk to resolve the user interface and friendly issues. |
Future Custom Browser era |
Browsers in the browser Flex Big development SL Big Development Custom ActiveX big development JavaScript fading |
Server further weakening, weakening to provide the necessary services for the front desk, Application Center transfer |
Through Ajax technology, using tools such as DWR. The browser finally grasped the full initiative of the application. |
On the whole, the development of the whole application architecture embodies the regression process from the ideal B/s architecture to the C/s architecture.