By Ilya Grigorik on March 22, 2010 Event-driven programming requires a mind-shift in how you architect the program, and oftentimes directly affects the choice of language, drivers, and even frameworks you can use. Most commonly found in highly interactive applications (GUI, network servers, etc), it usually implements the reactor pattern to handle concurrency in favor of threads: the âreactorâ is
{{#tags}}- {{label}}
{{/tags}}