--- a/src/transport.h Sun May 03 17:16:30 2009 +0300
+++ b/src/transport.h Sun May 03 17:18:16 2009 +0300
@@ -24,7 +24,7 @@
* These implement unbuffered I/O, so they may do partial reads/writes. In terms of the system read/write calls, the
* main difference is in the error return codes. On EOF, instead of returning zero, they return ERR_EOF (or
* ERR_WRITE_EOF for transport_write, for whoever knows what that means...). This means that when the underlying
- * transport is unable to fufill the request due to lack of data/buffer space, these can return zero to signifiy s
+ * transport is unable to fufill the request due to lack of data/buffer space, these can return zero to signifiy
* something simliar to EAGAIN.
*
* The transport API also implements non-blocking/event-based operation (usually on top of libevent), although at a
@@ -40,7 +40,7 @@
* the socket (i.e. normal select() semantics). If masked out using transport_events(), there should be no event
* activity on the transport (i.e. the fd read event is removed).
*
- * For writes, the transport maintains a write event that is disabled by default. If on_write returns zero, it will
+ * For writes, the transport maintains a write event that is disabled by default. If transport_write() returns zero, it will
* become enabled *once*, and consequently trigger transport_callbacks::on_write *once*, after which you must call
* transport_write() to possibly enable it again. If masked out using transport_events(), transport_write() will not
* enable the write event, and any pending write event is cancelled. If masked back in using transport_events(), the
@@ -131,8 +131,6 @@
* returns the number of bytes written (which may be less than \a len). If the transport is nonblocking, and the
* operation would have blocked, no data will be written, and zero is returned.
*
- * XXX: behaviour of transport_callbacks::on_write?
- *
* On errors, this returns the negative error code, along with extended info via \a err.
*
* @param transport the transport state