It is not difficult to recognize that picture / multimedia and long literals in web applications have largely determine the performance and load capacity of the in the middle.
While dealing with the picture uploads, these days are also considering the most reasonable storage of pictures and long text. Many years ago, I like to keep the pictures and long texts in Oracle, the purpose is to backup, only EXP can be reserved together, do not take care of the directory one by one. However, the disadvantage is also displayed as the visitor rises: one is greatly added to the burden of the database server; second to use blog / clog is not the standard SQL supported by SQL92, which makes the development of persistence are complex; Third, Oracle is not a database that is suitable for storing files. It can only support four thousand characters like his VARCHAR2, and use clob can't use SQL display directly; There is no storage limit, but also you can read and search for standard SQL. For graphic information, the transaction is not important, and the convenient query and speed (meaning low load) are more important, but it is upgraded to use BerklneyDB, adding transaction rollback, etc., becoming the tiger is not a traverse dog. Oracle, it should make it exclusively with a high-risk reliability requirement. Some friends think that the long text and pictures should be placed outside the database, through the connection reference, I think it is basically a graphic file system for MySQL, which is basically a graphic file system, with a SQL interface, so the text does not have to save outside Place the most suitable in MySQL. And the picture requires special blog processing, and the standard SQL cannot be used, it should be placed outside the database, reducing the burden of the system. Today's database usage and development model is actually a step forward to object-oriented storage and processing, especially in Java (which is the main working language of middleware), whether it is J2EE or Hibernate, or I have The DAO / Processor is all assessed by the Java object pool as an extension of the database object to the language platform, and the direct object-oriented storage replaces the specific data accessed via SQL. Although the data object itself is in the form of a relationship, it is hidden by the automatic initialization of the Java object. Therefore, as minimaing standardization (do not use a unique storage mode), it can greatly improve performance, simplify data objectization, which actually improves its reliability. Because of this, the picture is stored in a file system rather than binary, it is a more reasonable choice. Now my web platform is mainly using apache_catalina, this platform has been used in a few years ago, in fact, it not only change, but also the document is extremely lacking - even I can't find the server now. The definition of the Context object property in .xml. At the beginning, Apache was connected to the AJP13, which is said to be because Apache handles static files are far stronger than Tomcat, but I have never understood what the file is Apaci, what file is Tomcat? In fact I want the most Key files are worker.properties
Info = ajp13 forwarding over sockettomcatid = localhost: 8009 [URI: / JSP-Examples / *] [shm:] disabled = 1
If the URI: / jsp-example / * is like, I believe that Apache fart is not used, and it is Tomcat to bear everything. Obviously, if it is configured, the burden on the system, I refer to the Java server, will be greatly exceeded. The above configuration should be modified, allowing the Apache, but mainly HTML and pictures, and multimedia download tasks, not Tomcat, estimated to provide this matching system load capacity. ...... Write here, suddenly I feel that this configuration is quite eye-catching, hurry to check it, and the settings in the project are like this, but further testing makes me a little bit, I will prove it. That, I will show that it is. Software This thing is nothing to do if there is no logic inevitable connection. In any case, continue the above ideas, like the above configuration, indicating that all / JSP- Examples / * subtle directory is handed over to Tomcat processing; Apache does not work. The correct configuration should be: [URI: / JSP-EXAMPLES / *. JSP] [URI: / JSP-Examples / Servlet / *]
If you use such as Struts, you will probably need to add a suffix such as * .Action. This way, non-this type of file will be handed over to Apache. And this setting: [URI: / *] has a great danger, which will mean that all requests are responded by Tomcat; however, it seems that AJP13 makes preventive measures, in fact, then Hou Ajp13 throws all requests Entering the water, nothing. The negative effect is the root directory of the virtual host, I can't set it, it can directly identify Index.jsp. It can only be replaced with HTML, but it doesn't have anything big. If it is a small home page, you can turn it on the ground, and if it is a large home page, it will be the Timed conversion output as an HTML page.
Obviously, in this structure, it is most likely to match the running frame, but it is also wrong.