/*
- * $Id: HttpHeader.cc,v 1.41 1998/06/02 22:15:18 rousskov Exp $
+ * $Id: HttpHeader.cc,v 1.42 1998/06/03 15:52:15 rousskov Exp $
*
* DEBUG: section 55 HTTP Header
* AUTHOR: Alex Rousskov
httpHeaderPutInt(HttpHeader * hdr, http_hdr_type id, int number)
{
assert_eid(id);
- assert(Headers[id].type == ftInt); /* must be of an appropriatre type */
+ assert(Headers[id].type == ftInt); /* must be of an appropriate type */
assert(number >= 0);
httpHeaderAddEntry(hdr, httpHeaderEntryCreate(id, NULL, xitoa(number)));
}
httpHeaderPutTime(HttpHeader * hdr, http_hdr_type id, time_t time)
{
assert_eid(id);
- assert(Headers[id].type == ftDate_1123); /* must be of an appropriatre type */
+ assert(Headers[id].type == ftDate_1123); /* must be of an appropriate type */
assert(time >= 0);
httpHeaderAddEntry(hdr, httpHeaderEntryCreate(id, NULL, mkrfc1123(time)));
}
httpHeaderPutStr(HttpHeader * hdr, http_hdr_type id, const char *str)
{
assert_eid(id);
- assert(Headers[id].type == ftStr); /* must be of an appropriatre type */
+ assert(Headers[id].type == ftStr); /* must be of an appropriate type */
assert(str);
httpHeaderAddEntry(hdr, httpHeaderEntryCreate(id, NULL, str));
}
/*
- * $Id: HttpStatusLine.cc,v 1.11 1998/05/22 23:43:56 wessels Exp $
+ * $Id: HttpStatusLine.cc,v 1.12 1998/06/03 15:52:16 rousskov Exp $
*
* DEBUG: section 57 HTTP Status-line
* AUTHOR: Alex Rousskov
sline->reason = reason;
}
-/* parse a 0-terminating buffer and fill internal structires; returns true on success */
+/* parse a 0-terminating buffer and fill internal structures; returns true on success */
void
httpStatusLinePackInto(const HttpStatusLine * sline, Packer * p)
{
/*
- * $Id: MemBuf.cc,v 1.13 1998/06/02 04:18:14 wessels Exp $
+ * $Id: MemBuf.cc,v 1.14 1998/06/03 15:52:16 rousskov Exp $
*
* DEBUG: section 59 auto-growing Memory Buffer with printf
* AUTHOR: Alex Rousskov
*
* The whole "packing" idea is quite messy: We are given a buffer of fixed
* size and we have to check all the time that we still fit. Sounds logical.
- * However, what happens if we have more data? If we are lucky to be careful
- * to stop before we overrun any buffers, we still may have garbage (e.g.
- * half of ETag) in the buffer.
+ *
+ * However, what happens if we have more data? If we are lucky to stop before
+ * we overrun any buffers, we still may have garbage (e.g. half of ETag) in
+ * the buffer.
*
* MemBuffer:
* ----------
/*
- * $Id: Packer.cc,v 1.6 1998/03/03 22:17:52 rousskov Exp $
+ * $Id: Packer.cc,v 1.7 1998/06/03 15:52:17 rousskov Exp $
*
* DEBUG: section 60 Packer: A uniform interface to store-like modules
* AUTHOR: Alex Rousskov
* comm_write or "append" things to store, depending on actual packer
* supplied.
*
- * It is amasing how much work a tiny object can save. :)
+ * It is amazing how much work a tiny object can save. :)
*
*/
/*
- * $Id: disk.cc,v 1.117 1998/05/30 19:43:06 rousskov Exp $
+ * $Id: disk.cc,v 1.118 1998/06/03 15:52:18 rousskov Exp $
*
* DEBUG: section 6 Disk I/O Routines
* AUTHOR: Harvest Derived
return;
debug(6, 3) ("diskHandleWrite: FD %d\n", fd);
/* We need to combine subsequent write requests after the first */
- /* But only if we don't need to seek() in betwen them, ugh! */
+ /* But only if we don't need to seek() in between them, ugh! */
/* XXX This currently ignores any seeks (file_offset) */
if (fdd->write_q->next != NULL && fdd->write_q->next->next != NULL) {
len = 0;