Lesson plan

Libevent

libevent is a software library that provides asynchronous event notification. The libevent API provides a mechanism to execute a callback function when a specific event occurs on a file descriptor or after a timeout has been reached. libevent also supports callbacks triggered by signals and regular timeouts. libevent is meant to replace the event loop found in event-driven network servers. An application can just call event_dispatch() and then add or remove events dynamically without having to change the event loop. Currently, libevent supports /dev/poll , kqueue(2) , POSIX select(2) , Windows IOCP, poll(2) , epoll(7) and Solaris event ports. It also has experimental support for real-time signals. The exposed event API is uniform over all of the supported platforms. As a result, libevent allows for portable application development and provides "the most scalable event notification mechanism available on an operating system". Using callbacks on signals, libevent makes it possible to write "secure" signal handlers as none of the user supplied signal handling code runs in the signal's context. libevent was created by Niels Provos, and is maintained primarily by Azat Khuzhin. It is released under a BSD license.…

Back to article

Article summary

libevent is a software library that provides asynchronous event notification. The libevent API provides a mechanism to execute a callback function when a specific event occurs on a file descriptor or after a timeout has been reached. libevent also supports callbacks triggered by signals and regular timeouts. libevent is meant to replace the event loop found in event-driven network servers. An application can just call event_dispatch() and then add or remove events dynamically without having to change the event loop. Currently, libevent supports /dev/poll , kqueue(2) , POSIX select(2) , Windows IOCP, poll(2) , epoll(7) and Solaris event ports. It also has experimental support for real-time signals. The exposed event API is uniform over all of the supported platforms. As a result, libevent allows for portable application development and provides "the most scalable event notification mechanism available on an operating system". Using callbacks on signals, libevent makes it possible to write "secure" signal handlers as none of the user supplied signal handling code runs in the signal's context. libevent was created by Niels Provos, and is maintained primarily by Azat Khuzhin. It is released under a BSD license.…

Key claims

  1. release date: 2012-04-03 — source: Wikipedia · confidence 0.95
  2. release date: 2009-04-17 — source: Wikipedia · confidence 0.95
  3. release date: 2007-11-11 — source: Wikipedia · confidence 0.95
  4. release date: 2007-02-15 — source: Wikipedia · confidence 0.95
  5. release date: 2006-10-15 — source: Wikipedia · confidence 0.95
  6. release date: 2005-05-14 — source: Wikipedia · confidence 0.95

Discussion questions

  1. Summarise the article in your own words. Which single claim would you verify first, and why?
  2. The record states that the release date is "2012-04-03". What evidence would count against this claim?
  3. The record states that the release date is "2009-04-17". What evidence would count against this claim?
  4. The record states that the release date is "2007-11-11". What evidence would count against this claim?
  5. The record states that the release date is "2007-02-15". What evidence would count against this claim?
  6. The record states that the release date is "2006-10-15". What evidence would count against this claim?
  7. The record states that the release date is "2005-05-14". What evidence would count against this claim?
  8. Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
  9. If two sources disagreed about one of these facts, what would you need in order to trust one over the other?

Bibliography

No sources recorded.

Key claims and bibliography are generated from the same tracked claims and sources as the article page.