save events
This commit is contained in:
parent
86a79ef0a4
commit
506aecf4d5
1 changed files with 6 additions and 6 deletions
12
zk/events.md
12
zk/events.md
|
@ -1,4 +1,6 @@
|
||||||
---
|
---
|
||||||
|
id: events
|
||||||
|
aliases: []
|
||||||
tags:
|
tags:
|
||||||
- backend
|
- backend
|
||||||
- node-js
|
- node-js
|
||||||
|
@ -15,12 +17,10 @@ Another way of putting this is to say that all events in Node inherit from the
|
||||||
event. At bottom everything in Node is an event with a callback, created via
|
event. At bottom everything in Node is an event with a callback, created via
|
||||||
event emitters.
|
event emitters.
|
||||||
|
|
||||||
Because Node's runtime is
|
Because Node's runtime is [event-driven](Event_loop.md), it is event-emitter
|
||||||
[event-driven](Event_loop.md), it is
|
cycles that are being processed by the Event Loop, although you may know them as
|
||||||
event-emitter cycles that are being processed by the Event Loop, although you
|
`fs` or `http` (etc) events. The call stack that the Event Loop works through is
|
||||||
may know them as `fs` or `http` (etc) events. The call stack that the Event Loop
|
just a series of event emissions and their associated callbacks.
|
||||||
works through is just a series of event emissions and their associated
|
|
||||||
callbacks.
|
|
||||||
|
|
||||||
## Event Emitters
|
## Event Emitters
|
||||||
|
|
||||||
|
|
Loading…
Add table
Reference in a new issue