X-Git-Url: https://git.dogcows.com/gitweb?a=blobdiff_plain;f=notes.txt;h=6b732a6f54b44de687634bea5df81339c0a1ffbe;hb=e9a895bf42ef9b706aba2d2770ae61dad28ea9a4;hp=16f2f5c0439b4377c8ed931153d5255c126e2932;hpb=1e5589cbb1518565f28a66bafd4882eec1d9acd5;p=chaz%2Ftalk-event-driven-programming-in-perl diff --git a/notes.txt b/notes.txt index 16f2f5c..6b732a6 100644 --- a/notes.txt +++ b/notes.txt @@ -27,9 +27,10 @@ X kernel facilities (poll, select, etc.) - Mojo::IOLoop 6. Special considerations -- Exceptions in event-driven code. -- SIGPIPE, EPIPE - might have more to do with long-lived processes rather than +X Exceptions in event-driven code. +X SIGPIPE, EPIPE - might have more to do with long-lived processes rather than just event-driven programming, but still something to watch out for... +X You should almost always check the return code of your syscalls to see if they succeeded or not. 7. Promises: - Future @@ -51,6 +52,7 @@ X What is event-driven programming? - C10k problem - EDA (event-driven architecture) - Benefits of Event-driven +- How to debug event-driven code. Traditional programs: - CGI - web server calls your program, and your program does its thing and