HTML5 worker Multithreading

Test Browser: FF 3.6 test server: APACHE 2.2 let's assume that if multithreading can be used on the WEB page, does it mean that the WEB page gradually replaces the client? After HTML5 specifications are completed, the multi-thread WEB is a Xiami? Literally, we should see that its implementation is the WORKER mode. What is the WORKER mode? Those who have written multithreading should be clearer than me. The general concept is that the creation of a thread is determined by a WORKER and a thread pool is maintained. Next, let's take a look at the features of HTML5 multithreading: 1. DOM nodes cannot be operated in the thread (messages can only be sent to the worker creator's callback function if you want to operate. the essence of Multithreading is actually a real system thread. functions such as setTimeout (), clearTimeout (), setInterval (), and clearInterval () can be used. the general process of performing I/O operations (ajax) worker is like this: Create a worker object and bind it to the onmessage method that receives messages from the background and the onerror method onerror. Use postMessage to transmit data. The parameters of this method are strict JSON objects. When the background processing is complete, use the postMessage method to send data back to the foreground, that is, the onmessage method. Next let's look at the example: in this example, A number is passed on the page to add 3 to the background, and then the caller is displayed on the page: <! DOCTYPE html>