官术网_书友最值得收藏!

Managing concurrency

Simplifying control flows has been a concern of the Node community since the very beginning of the project. Indeed, this potential criticism was one of the very first anticipated by Ryan Dahl, who discussed it at length during the talk in which he introduced Node to the JavaScript developer community.

Because deferred code execution often requires the nesting of callbacks within callbacks, a Node program can sometimes begin to resemble a sideways pyramid, also known as The Pyramid of Doom. You've seen it: deeply nested code, 4 or 5 or even more levels deep, curly braces everywhere. Apart from syntactical annoyances, you can also imagine that tracking errors across such a call stack might be difficult—if a callback at the third level throws, who is responsible for handling that error? The second level? Even if level 2 is reading a file and level 3 is querying a database? Does that make sense? It can be hard to make sense of asynchronous program flows.

主站蜘蛛池模板: 西藏| 云安县| 达日县| 高邑县| 和田县| 新化县| 伊金霍洛旗| 三门县| 吐鲁番市| 措勤县| 平度市| SHOW| 那曲县| 和顺县| 蕉岭县| 沈阳市| 凤山县| 香港| 永寿县| 台州市| 咸丰县| 宣威市| 常山县| 兴国县| 泾源县| 农安县| 胶州市| 益阳市| 尚义县| 方山县| 枣强县| 景洪市| 韶山市| 嵊泗县| 天台县| 阿克苏市| 丹棱县| 衢州市| 葵青区| 天等县| 中牟县|