The meaning of HTML document structure to DIV+CSS layout

The difference between get and post in form submission is 5 points
1.get is getting the data from the server, and the post is transferring data to the server. The
2.get is to add the parameter data queue to the URL referred to in the action attribute of the submission form, and the value corresponds to each field one by one in the form, as you can see in the URL. Post is the httppost mechanism by which each field in the form is placed with its contents in the HTML header and routed to the URL address referred to by the action attribute. This process is not visible to the user.
3. For Get mode, the server end uses Request.QueryString to obtain the value of the variable, and for the Post method, the server end uses Request.Form to obtain the submitted data. The
4.get transmits a small amount of data and cannot be greater than 2KB. Post transfers have a large amount of data, which is generally default to unrestricted. In theory, however, the maximum number of IIS4 is 100KB in 80KB,IIS5.
5.get Security is very low and post security is high.

HTTP Request: The difference between get and post methods
HTTP defines different methods of interacting with the server, and the most basic method is get and post. In fact, get applies to most requests, while the reserved post is used only for updating the site. According to the HTTP specification, get is used for information acquisition, and should be secure and idempotent. The so-called safe means that the operation is used to  rather than modify information. In other words, get requests should not generally have side effects. Idempotent means that multiple requests to the same URL should return the same result. The complete definition is not as strict as it seems. Fundamentally, the goal is that when a user opens a link, she can be sure that it doesn't change resources from its perspective. For example, the front pages of news sites are constantly being updated. Although the second request returns a different batch of news, the operation is still considered safe and idempotent, as it always returns the current news. Vice versa. Post requests are not that easy. Post represents a request that might change resources on the server. Still, for example, a news site, the reader's note to the article should be implemented through a POST request, because the site has been different after the annotation was submitted (for example, an annotation appears below);
When the form is submitted, if method is not specified, the default is GET request. The data submitted in the form will be appended to the URL and separated from the URL. Alphanumeric characters are sent as is, but spaces are converted to "+", and other symbols are converted to%XX, where XX is the ASCII (or ISOLatin-1) value of the symbol in the 16 binary notation. A GET request requests that the data submitted be placed in the HTTP request protocol header, while the data submitted by the post is placed in the Entity data, and the
Get method submits a maximum of 1024 bytes of data and the post does not have this limit.
What is the difference between using "post" and "get" in a form
in the form, you can use post or get. They are all valid values of method. However, the post and get methods are used at least two points differently:
1, the Get method passes the user's input through a URL request. The Post method is in another form.
2, get mode of submission you need to use Request.QueryString to obtain the value of the variable, and when the Post method is submitted, you must access the submitted content through Request.Form. The
carefully study the following code. You can run it to feel:
Code
〈!– Two FORM only the method property differs –〉
〈form action= "getpost.asp" method= "get"?
〈input type= "text" name= "text" value= "Hello World" 〉〈/input〉
〈input type= "Submit" value= "Method=get" 〉〈/input〉< br>〈/form〉
〈br〉
〈form action= "getpost.asp" method= "POST"
〈input type= "text" name= "text" value= "Hello worl D "〉〈/input〉
〈input type=" Submit "value=" Method=post "〉〈/input〉
〈/form〉
〈br〉
〈br〉
〈% If request.que Rystring ("text") 〈〉 "" Then%〉
The string passed through the Get method is: "〈b〉〈%= request.querystring (" text ")%〉〈/b〉" 〈br〉
〈% end If%〉
〈% If Request.Form ("Text") 〈〉 "" Then%〉
is primarily my reflection on the contradiction between structure and development efficiency, a question of how the CSS framework can not break the ring structure. And for structure and efficiency my point of view is that "having a reasonable structure is the fundamental motivation for your web standardization", and that the web is the bearer of information, and there is no reason to compromise a reasonable structure for visual effects.  

Web standards to grasp a few points:

Use structured, semantically labeled
Using CSS to isolate performance elements in (X) HTML documents
Rely on JavaScript to enhance, not replace, the characteristics of the site (for example, if CSS does not, give JavaScript instead of replacing CSS to do what he can do)

For the structure of a variety of combinations I have been very disgusted, maybe I do not understand the depth of the understanding of his benefits, perhaps a reasonable combination of structure and development efficiency, but I did not find, I will be inconsistent.

This is the way the style is grouped
<div class= "Class1 class2 ... classn" ></div>
Give me a layout example
<div class= "F-left w400 bgfff" >
Several classes are grouped into a left-floating, wide 400 background for a white area

You may have a huge library, the page only needs a combination of any class can be completed, eliminating most of the time spent on CSS, but the result is the structure of chaos, the difficulties of revision, or even backward compatibility is limited. This is the same as the table layout, but the code looks good, and the amount of code difference is not too big. In the early days of applying web standards, a reasonable table layout is also allowed.

So many classes remind me of the long table attributes.

<table border=0 cellpadding=0 cellspacing=0 align=center width=100%

Is the hard work is to use DIV with CSS to simulate a table is easy to achieve the effect? and achieve the same poor table layout?

Semantics is also a part of the structure, in addition to the rational use of (X) HTML markup Language, ID is a part of the semantic component, div ID is like an instant sticker, tell you the semantics of a Div, tell you the meaning of this block.

Micro-format (microformat) is a new way of embedding structured data in standard XHTML code. His birth is also very clear that the structure of the web is always the first, the advantages of semantics is very realistic embodiment, Div's attribute planning also embodies the semantics, not just a pass to the style work interface. Take a look at the IBM Documentation Center, "separating data and formatting using microformats" to understand how it works.