From 4e5ad6d5ee9e72ddf6550a6795c18039b265e501 Mon Sep 17 00:00:00 2001
From: Diego Nehab
-The LuaSocket API was designed with two goals in mind. First, users +The API design had two goals in mind. First, users experienced with the C API to sockets should feel comfortable using LuaSocket. Second, the simplicity and the feel of the Lua language should be preserved. To achieve these goals, the LuaSocket API keeps the function names and semantics the C API whenever possible, but their usage in Lua has been greatly simplified. @@ -94,7 +94,7 @@ call might perform several OS calls, so that the two timeout values are Finally, the host name resolution is transparent, meaning that most functions and methods accept both IP addresses and host names. In case a host name is given, the library queries the system's resolver and -tries the main returned IP address. Note that direct use of IP addresses +tries the main IP address returned. Note that direct use of IP addresses is more efficient, of course. The toip and tohostname @@ -299,14 +299,14 @@ io.write(socket.try((udp:receive()))) -
LuaSocket offers much more than TCP and UDP support. As the library +
Although not covered in the introduction, LuaSocket offers +much more than TCP and UDP functionality. As the library evolved, support for HTTP, FTP, -SMTP, MIME, URLs and much more was made available. These are -mostly implemented in Lua itself, with critical parts implemented in C for -efficiency
+and SMTP were built on top of these. These modules +and many others are covered by the reference manual. + -- cgit v1.2.3-55-g6feb