Discussion: the JS page Jump

rt, The artist brought a static page, the dynamic part by reading the XML generation on the page.

If using the traditional CGI method, the static page and the dynamic data generated by CGI together from the server back to the browser display.

If I put a fixed folder all static page on the server, when accessing a page always through the JS editor URL, location.href=***.html? Qurey1=value1& query2=value2 page, and then in the next page request to the CGI XML file and returns, whether this will lighten the burden of CGI? Because the static part is obtained directly through the fixed URL.

If you can, why still need to CGI every time the static part of the code is returned to the client?
The two is what the advantages and disadvantages of each.?

Started by Virgil at November 12, 2016 - 8:14 PM


Posted by Virgil at November 21, 2016 - 8:57 PM

I use CGI to dynamic pages and static page to return is not known to have XML. . .

Know XML, I use JavaScript+html storage, after loading the page JavaScript request CGI, CGI print XML to JavaScript.

No other good way to temporarily, just make do with.

Posted by Rupert at November 26, 2016 - 9:10 PM