3 - Get more knowledge about the Reactor front ends.
4 - Throw up some examples in some slides (#5).
5 - Add a section at the end to get out of the weeds and put a bit ol' bow on it.
9 1. Evolution of event-driven programming:
10 X Wait for a key press or line of text.
11 X Interrupts (hardware and software).
14 2. Types of events in modern applications:
19 X Anything that can spontaneously happen in the real world.
21 3. How to write a modern event-loop (reactor style).
22 X kernel facilities (poll, select, etc.)
24 4. List of already-built reactors.
29 5. Event-driven programming in Perl
35 6. Special considerations
36 X Exceptions in event-driven code.
37 X SIGPIPE, EPIPE - might have more to do with long-lived processes rather than
38 just event-driven programming, but still something to watch out for...
39 X You should almost always check the return code of your syscalls to see if they succeeded or not.
46 8. Real-world uses for event-driven applications:
55 X What is event-driven programming?
56 X Reactor: event loop that can receive multiple types of events and
57 demultiplex them, delivering them to appropriate handlers.
59 - EDA (event-driven architecture)
60 X Benefits of Event-driven
61 X How to debug event-driven code.
64 - CGI - web server calls your program, and your program does its thing and
66 X filters - grep, less, sed, etc. Like a function, the program takes its input
67 and produces some output.
70 - first-class subroutines
72 - Can mix traditional architecture with event-driven (like docker that
73 provides both an http and command-line interface.