summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorEmil Renner Berthing <esmil@mailme.dk>2013-02-01 02:36:52 +0100
committerEmil Renner Berthing <esmil@mailme.dk>2013-02-01 02:36:52 +0100
commit176c0bde4140fa0c3403d19c11eb32dc456bf7ad (patch)
treef88406c62e3d000bd0f539556a9e1b71d2c34f2c
parent12dcbfd162e9dc665d857c2172b68651498f373f (diff)
downloadlem-176c0bde4140fa0c3403d19c11eb32dc456bf7ad.tar.gz
lem-176c0bde4140fa0c3403d19c11eb32dc456bf7ad.tar.xz
lem-176c0bde4140fa0c3403d19c11eb32dc456bf7ad.zip
README: refer to the example
-rw-r--r--README.markdown3
1 files changed, 3 insertions, 0 deletions
diff --git a/README.markdown b/README.markdown
index 6c9e7a7..3fd8159 100644
--- a/README.markdown
+++ b/README.markdown
@@ -65,6 +65,9 @@ to happen before resuming the coroutine.
This allows libraries to be written such that calls appear to be blocking,
while still allowing other Lua coroutines to run. It also allows you to write
libraries which automatically spawn new coroutines to handle incoming events.
+In the above example the autospawn method automatically spawns new coroutines
+to handle incoming connections, and the read and write methods suspends the
+the running coroutine while waiting for I/O.
For this to work properly LEM modules needs to use non-blocking I/O. However,
not all I/O can easily be done non-blocking. Filesystem operations is one example.