Talk:Event-driven programming

message: The section on "Exception handlers" talks about PL/1! Why PL/1?  It is hardly the programming language to be cited, unless possibly for historical reasons.  Todd (talk) 16:52, 13 May 2014 (UTC)
thread_title: PL/1?!

message: It would be helpful to discuss server architecture in more detail, given this subject will help ground some of the principles of event driven programming, perhaps drawing on the content from Benjamin Erb thesis, http://berb.github.io/diploma-thesis/community/042_serverarch.html#event
As an alternative to synchronous blocking I/O, the event-driven approach is also common in server architectures. Due to the asynchronous/non-blocking call semantics, other models than the previously outlined thread-per-connection model are needed. A common model is the mapping of a single thread to multiple connections. The thread then handles all occurring events from I/O operations of these connections and requests. 
--Nigel V Thomas (talk) 14:49, 19 May 2013 (UTC)
thread_title: Proposal for a new subsection on event driven server architecture

message: This is the worst Wikipedia article I've ever seen.  In light of the popularity of node.js, and the increasing importance of this concept, it would be really nice to see a proper article on the subject.  Maybe asking too much.  Alas.
:I'd dispute that node.js is related to the increasing importance of Event-driven programming. At TIBCO software (Teknekron Software Systems at the time) we were we were changing how stock and similar trading systems worked in the early '90s by using combining messaging techniques and event-driven concepts.
:As is typical in software engineering, ideas and concepts repeatedly emerge as new and revolutionary and it is wise to look back in history to find why they fell out of favor in the past. IBM probably discovered and experimented with almost all technologies we "discover" nowadays, even if they may not have been widely adopted in the past. In most cases, techniques like event-driven solve some problems that exist with the technology they replace, however, they bring a different set of problems that may not be obvious initially. As usage increases and time passes, folks will start using node.js for problems that are not well matched to event-driven architectures and complexity will increase... until somebody will find a new solution such as distributed work queues or agent pools or...
::--Bwhateley (talk) 14:30, 10 February 2018 (UTC)
thread_title:  Ugh 

message: It was on the same subject, but improperly titled.  The EDPL page was (IMO) much more informative, so its content is now dominant.  This page could be improved by 
# Better real-world examples of ways to use EDP (I suspect the socket example may be one, but I am not at all versed in the subject.
# Linking the description of EDP to the references.
Nate 16:24, 6 December 2006 (UTC)
thread_title:  Merged all content from [[Event driven programming language]] 

message: I think a paragraph in event-driven programming vs. threading would be good, since they are often confused. Anyone? 72.140.200.178 17:56, 16 December 2006 (UTC)
thread_title:  Events vs. Threading 

message: ----
Event in Computing should not be merged with Event Notification (or Event Driven Architecture) as the latter is used only in the enterprise application integration(EAI). A keyboard or mouse event (as given in the Wikipedia example) should not be compared with event that criss cross enterprise systems. (L.Sukumaran - 27-Aug-08).
---  —Preceding unsigned comment added by 203.158.94.82 (talk) 06:45, 27 August 2008 (UTC)
thread_title:  merger proposal 

message: I find this assertion highly dubious:
Hardware description language (like Verilog and VHDL) are essentially multi-threaded programming languages based on an event-driven paradigm
HDLs are not anywhere near to "threaded" programming languages (threads run on a processor connected to a memory stack, while HDLs are directly translated to hardware), and their paradigm is more "continuous" than "event-driven". I think this should be explained with much more clarity for it to stay in the article, otherwise I can't see how event-driven relates to this kind of languages. Diego (talk) 20:51, 16 June 2008 (UTC)
replies: text: I have just finished a blog entry, that explains how HDLs outperform the conventional, serial, programming in reaction to state change and would like to defend the assertion. At first, though the programming threads are much "heavier" than the HDL processes, they are known as lightweight process. Secondly, the HDLs, VHDL for sure, do heavily rely on the notion of "event" to drive the processes: one signal change causes change of other signals that depend on it and so on. The simulation goes on as long as there are any events scheduled to simulate. --Javalenok (talk) 10:46, 5 June 2010 (UTC)
replies: text: The link in the above comment is now dead. GeneCallahan (talk) 06:01, 9 September 2015 (UTC)

text: Take a major HDL, the VHDL. Its semantics is defined for (delta-cycle) simulation. Literally, "The simulation philosophy of VHDL is based on the ordering of events in time: new events are generated as result of actions taken in response to other events scheduled for previous simulation times." The simulation runs until there is at least one event in the queue. This is literal meaning of 'event-driven'. So, the HDL is true (asynchronous) event-driven by nature. Any synchronization is implemented 'on top'. So, despite most of HW might be synchronous, it does not mean that HDLs are. Neither organizing the boolean operators and larger processors into a dataflow network (VHDL "programming" is description of HW circuit indeed rather than explicit event specification) implies the circuit model is evaluated in fashion different from event driven. The article definition requires only program behaviour to be determined by events rather than the programming style. In Java or Delphi, you register the event handlers explicitly. As I mentioned above, this is 'syntactic salt'. Got rid of it, you'll get the sugar, the event-driven friendly HDL dataflow style. --Javalenok (talk) 14:36, 12 October 2010 (UTC)
thread_title:  What do hardware languages have to do? 

message: Edits from December 2010 have replaced criticism of Event-driver programming with something that appears rather dubious, or at least extremely unclear.
I'm most bothered by the line "doesn't try to have shared memory problems that can be solved with fancy algorithms," which sounds like pure snark. But I don't know a thing about this subject, so maybe I'm just misunderstanding what it tries to do (or what's being snarked at). 
Can somebody please examine the edit, and clarify or revert as necessary? Standback (talk) 07:53, 21 February 2011 (UTC)
thread_title:  "Fertile Ground For Bugs" edit 

message: In the Criticism and best practice section, the links for ripple effects are not helpful.  The wikipedia link provides no useful description beyond the barest summary and the article linked to in the reference note only refers to the subject indirectly and implicitly (and never by this name).
User:itsbruce  —Preceding undated comment added 19:37, 24 September 2012 (UTC)
thread_title:  Poor References with regard to Ripple Effects 

message: This link leads me to a general page on the Eiffel language. GeneCallahan (talk) 05:41, 9 September 2015 (UTC)
thread_title:  Event-Driven Programming and Agents, chapter 

message: Hello fellow Wikipedians,
I have just modified one external link on Event-driven programming. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive https://archive.is/20121208205239/http://zone.ni.com/devzone/devzone.nsf/webcategories/FCE7EA7ECA51169C862567A9005878EA to http://zone.ni.com/devzone/devzone.nsf/webcategories/FCE7EA7ECA51169C862567A9005878EA
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
Cheers.—InternetArchiveBot (Report bug) 16:35, 25 September 2017 (UTC)
thread_title:  External links modified 

message: This reference appears to be broken: https://en.wikipedia.org/wiki/Event-driven_programming#cite_note-Samek-2
This external source has the same title and author, but the content appears largely redundant with another reference ("State Machines for Event-Driven Systems"): https://www.state-machine.com/doc/Samek0304.pdf  — Preceding unsigned comment added by Joee92 (talk • contribs) 20:31, 23 September 2019 (UTC)
thread_title:  Broken Reference 

message: The criticism section of the article presents the use of Petri nets as a solution for problems with event-driven programming.
:A solution for this is to use Petri nets.
Reading this section it is not clear to me which of the problems mentioned in the paragraph are solved by Petri nets and how. There is also no source for the claim and the linked Wikipedia article focuses on Petri nets as a mathematical modeling language while the Event-driven programming article is focused on computer programming.
2A02:8388:8C40:800:6CBB:8583:3317:FBB5 (talk) 11:40, 31 May 2021 (UTC)
replies: text: That's why I removed the whole paragraph. RolandIllig (talk) 19:25, 15 April 2024 (UTC)
thread_title:  Reference to Petri nets