Editing Event-driven programming (section)

==Common uses==
Most existing GUI architectures use event-driven programming.<ref name="Samek">{{Cite news|url=http://www.ddj.com/cpp/184401643|title=Who Moved My State?|last=Samek|first=Miro|date=April 1, 2013|work=Dr. Dobb's|access-date=2018-01-28}}</ref> Windows has an [[Message loop in Microsoft Windows|event loop]]. The Java AWT framework processes all UI changes on a single thread, called the [[Event dispatching thread]]. Similarly, all UI updates in the Java framework [[JavaFX]] occur on the JavaFX Application Thread.<ref>{{cite web
 |url=https://docs.oracle.com/javafx/2/threads/jfxpub-threads.htm
 |title=Concurrency in JavaFX
 |last=Fedortsova
 |first=Irina
 |date=June 2012
 |website=JavaFX Documentation Home
 |publisher=Oracle
 |access-date=4 January 2018
 |quote=The JavaFX scene graph, which represents the graphical user interface of a JavaFX application, is not thread-safe and can only be accessed and modified from the UI thread also known as the JavaFX Application thread. }}</ref>

Most network servers and frameworks such as Node.js are also event-driven.<ref>[https://www.digitalocean.com/community/tutorials/nodejs-event-driven-programming/ Event-Driven Programming in Node.js].</ref>