web执行流程(国外英语资料).docVIP

web执行流程(国外英语资料) Clearly a WEB request in detail through SSH framework, the FILTER + WEB. XML, including the JSP and SERVLET scheduling process, Tomcats thread pool and JDBC connection pool, struts 2 interceptor and automatic assembly mechanism and related classes involved, SPRINGs transaction, AOP, and automatic assembly and related classes involved, HIBERNATE CACHE and automatic assembly mechanism and transaction; A. The JSP request Browser requests: Generally have the POST and GET methods, both in the same process, only one of them so often in the Servlet end, and then in another way to call the implemented method; The difference is: (1) parameter length: The GET method parameter is in the browser address bar, so there is a length limit; Right? Separate the paths and parameters, and separate the parameters; The argument to the POST method is in the message body, so there is no length limit; (2) security The parameters of the GET method are shown in the address bar, so they are not secure; The parameters of the POST method are in the message body, not visible, and therefore more secure; (3) the bookmarks GET can be established, and POST cannot be established; (4) power etc. In theory, the GET method should be a power (repeatable to perform multiple non-side effects), and the POST method is not a power. (5) the transcoding distinction In practice found that the GET and POST there will be a problem, namely the parameters of the GET method usually need manual decoding, and POST is not required, the reason is that the application server code has not set up correctly, the default to the ISO - 8859-1; 2. After the Filter (1) in general, you need to pass the SPRINGs character set transcoding mechanism, CharacterEncodingFilter, to handle the situation in which the foreground JSP page differs from the background JAVA code encoding mechanism. (2) and then pass other filters, sometimes permissions and security validation, and more cases are directly intercepted by the STRUTS2