Skip to content

Commit

Permalink
Replace asynchronous occurrences with non-blocking
Browse files Browse the repository at this point in the history
Fixes: #35
  • Loading branch information
azat committed Feb 18, 2024
1 parent b25f133 commit a9ebd1c
Show file tree
Hide file tree
Showing 3 changed files with 6 additions and 6 deletions.
2 changes: 1 addition & 1 deletion 00_about.txt
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ include::license.txt[]
:language: C

This document will teach you how to use Libevent 2.0 (and later) to write fast
portable asynchronous network IO programs in C. We assume:
portable non-blocking network IO programs in C. We assume:

* That you already know C.
* That you already know the basic C networking calls (socket(),
Expand Down
8 changes: 4 additions & 4 deletions 01_intro.txt
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
:docinfo:

A tiny introduction to asynchronous IO
========================================
A tiny introduction to synchronous non-blocking IO
==================================================

include::license.txt[]

Expand Down Expand Up @@ -239,7 +239,7 @@ provides a consistent interface to various select() replacements,
using the most efficient version available on the computer where it's
running.

Here's yet another version of our asynchronous ROT13 server. This
Here's yet another version of our non-blocking ROT13 server. This
time, it uses Libevent 2 instead of select(). Note that the fd_sets
are gone now: instead, we associate and disassociate events with a
struct event_base, which might be implemented in terms of select(),
Expand Down Expand Up @@ -274,7 +274,7 @@ variables.
Moreover, if you're deeply experienced with networking on Windows,
you'll realize that Libevent probably isn't getting optimal
performance when it's used as in the example above. On Windows, the
way you do fast asynchronous IO is not with a select()-like interface:
way you do fast non-blocking IO is not with a select()-like interface:
it's by using the IOCP (IO Completion Ports) API. Unlike all the
fast networking APIs, IOCP does not alert your program when a socket
is _ready_ for an operation that your program then has to perform.
Expand Down
2 changes: 1 addition & 1 deletion TOC.txt
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ Learning Libevent
-----------------

- link:00_about.html[Chapter 0: About this document]
- link:01_intro.html[Chapter 1: A tiny introduction to asynchronous IO.]
- link:01_intro.html[Chapter 1: A tiny introduction to synchronous non-blocking IO]


A Libevent Reference Manual
Expand Down

0 comments on commit a9ebd1c

Please sign in to comment.