A brief discussion on Javascript threads and timing mechanisms

Home

Web Front-end

JS Tutorial

A brief discussion on Javascript threads and timing mechanisms_javascript skills

WBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWB

May 16, 2016 pm 03:51 PM

javascriptthread

Usage of setTimeout and setInterval

The second parameters of setTimeout and setInterval defined in the Javascript api document mean respectively the number of milliseconds after which the callback function is executed and the number of milliseconds after which the callback function is executed. But with the accumulation of work experience, we found that this is not the case.

For example

div.onclick=function(){
  setTimeout(function(){
     document.getElementById('input').focus(); 
  },0);
}

I can’t explain it. Just execute it immediately. Why do you need to set a timer to go around in circles?

Another day you wrote the following piece of code

setTimeout(function(){while(true){}},100);
setTimeout(function(){alert('你好');},200);

The first line of code loops endlessly, resulting in the second line of alert never appearing. Why?

Single thread or multi-thread?
It turns out that the JavaScript engine runs in a single thread, and the browser has only one thread running the JavaScript program. Because of the single-threaded design, complex multi-thread synchronization issues are eliminated.

When setting a timer, the browser will insert the callback function you specify into the task sequence after the set time instead of executing it immediately. If the timing time is set to 0, it means that the task sequence is inserted immediately instead of being executed immediately. You still have to wait for the tasks in the queue to be executed and it is your turn before you execute them.

So the following code pops up 2 first, then 1

setTimeout(function(){
  alert(1);
},0);
alert(2);

So, what is the practical use of this? Let’s take a look at the example below

<!DOCTYPE html>
<html>
  <head>
    <meta charset="utf-8">
    <meta name="viewport" content="width=device-width,initial-scale=1.0">
    <title>setTimeout 0</title>
  </head>
  <body>
    输入字符，但内容却不能实时显示<input type="text" onkeydown="show(this.value)"/> <br/>
    输入字符，内容能实时显示<input type="text" onkeydown="var self=this;setTimeout(function(){show(self.value)},0)"/>
    <div></div>
    <script>
      function show(val){
        document.getElementsByTagName("div")[0].innerHTML=val;
      }
    </script>
  </body>
</html>

In this example, the js engine needs to execute the keydown event handler and then update the value of the input box. When the event handler is executed, the task of updating the value can only enter the queue to wait, so the updated value cannot be obtained when the keydown event is executed; but through setTimeout we put the operation of getting the value into the queue and execute it after updating the value, so The content will be displayed in real time.

Come back and look at the following code:

setTimeout(function(){
  //do something...
   setTimeout(arguments.callee,10);
},10);

setInterval(function(){
  //do something...
},10);

These two pieces of code look to have the same effect, don’t they? In fact, there is a difference. The setTimeout in the callback function of the first paragraph is a new timing set after the js engine is executed. It is assumed that there is a time interval from the completion of the previous callback to the start of the next callback. Theoretically, the time interval > ;=10ms, the following code

Speaking of which, is XMLHttpRequest really asynchronous? Yes, the request is asynchronous, but this request is a new thread opened by the browser. When the requested state changes, if a callback has been set previously, the asynchronous thread will put the state change event into the js engine processing queue to wait for processing. When the task is processed, the js engine will always execute the function set by onreadystatechange in a single thread.

The above is the entire content of this article, I hope you all like it.

Statement

The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn

Python vs. JavaScript: Community, Libraries, and ResourcesApr 15, 2025 am 12:16 AM

Python and JavaScript have their own advantages and disadvantages in terms of community, libraries and resources. 1) The Python community is friendly and suitable for beginners, but the front-end development resources are not as rich as JavaScript. 2) Python is powerful in data science and machine learning libraries, while JavaScript is better in front-end development libraries and frameworks. 3) Both have rich learning resources, but Python is suitable for starting with official documents, while JavaScript is better with MDNWebDocs. The choice should be based on project needs and personal interests.

From C/C to JavaScript: How It All WorksApr 14, 2025 am 12:05 AM

The shift from C/C to JavaScript requires adapting to dynamic typing, garbage collection and asynchronous programming. 1) C/C is a statically typed language that requires manual memory management, while JavaScript is dynamically typed and garbage collection is automatically processed. 2) C/C needs to be compiled into machine code, while JavaScript is an interpreted language. 3) JavaScript introduces concepts such as closures, prototype chains and Promise, which enhances flexibility and asynchronous programming capabilities.

JavaScript Engines: Comparing ImplementationsApr 13, 2025 am 12:05 AM

Different JavaScript engines have different effects when parsing and executing JavaScript code, because the implementation principles and optimization strategies of each engine differ. 1. Lexical analysis: convert source code into lexical unit. 2. Grammar analysis: Generate an abstract syntax tree. 3. Optimization and compilation: Generate machine code through the JIT compiler. 4. Execute: Run the machine code. V8 engine optimizes through instant compilation and hidden class, SpiderMonkey uses a type inference system, resulting in different performance performance on the same code.

Beyond the Browser: JavaScript in the Real WorldApr 12, 2025 am 12:06 AM

JavaScript's applications in the real world include server-side programming, mobile application development and Internet of Things control: 1. Server-side programming is realized through Node.js, suitable for high concurrent request processing. 2. Mobile application development is carried out through ReactNative and supports cross-platform deployment. 3. Used for IoT device control through Johnny-Five library, suitable for hardware interaction.

Building a Multi-Tenant SaaS Application with Next.js (Backend Integration)Apr 11, 2025 am 08:23 AM

I built a functional multi-tenant SaaS application (an EdTech app) with your everyday tech tool and you can do the same. First, what’s a multi-tenant SaaS application? Multi-tenant SaaS applications let you serve multiple customers from a sing

How to Build a Multi-Tenant SaaS Application with Next.js (Frontend Integration)Apr 11, 2025 am 08:22 AM

This article demonstrates frontend integration with a backend secured by Permit, building a functional EdTech SaaS application using Next.js. The frontend fetches user permissions to control UI visibility and ensures API requests adhere to role-base

JavaScript: Exploring the Versatility of a Web LanguageApr 11, 2025 am 12:01 AM

JavaScript is the core language of modern web development and is widely used for its diversity and flexibility. 1) Front-end development: build dynamic web pages and single-page applications through DOM operations and modern frameworks (such as React, Vue.js, Angular). 2) Server-side development: Node.js uses a non-blocking I/O model to handle high concurrency and real-time applications. 3) Mobile and desktop application development: cross-platform development is realized through ReactNative and Electron to improve development efficiency.

The Evolution of JavaScript: Current Trends and Future ProspectsApr 10, 2025 am 09:33 AM

The latest trends in JavaScript include the rise of TypeScript, the popularity of modern frameworks and libraries, and the application of WebAssembly. Future prospects cover more powerful type systems, the development of server-side JavaScript, the expansion of artificial intelligence and machine learning, and the potential of IoT and edge computing.

See all articles