Hair up handling of HTTP headers. In new model, there are codecs for
authorChris Hanson <org/chris-hanson/cph>
Wed, 17 Sep 2008 06:31:54 +0000 (06:31 +0000)
committerChris Hanson <org/chris-hanson/cph>
Wed, 17 Sep 2008 06:31:54 +0000 (06:31 +0000)
commita4c0540ca381d86f8d49275fbc96837d56eabe61
tree7d9fbe1754b80929befb273c3a5adbad35ea71d1
parent516f8b04cc1388717c0bed93aaa3b68321347054
Hair up handling of HTTP headers.  In new model, there are codecs for
each known header (basically almost all of RFC 2616 at this point).
These codecs translate between the string representation of a header
value and its internal representation.  MAKE-HTTP-HEADER accepts
either the string representation or the internal representation.
HTTP-HEADER-VALUE always contains the string representation, while
HTTP-HEADER-PARSED-VALUE contains the internal representation.  If the
decoder for a header fails on a particular string represenation, or if
there's no decoder for that header, HTTP-HEADER-PARSED-VALUE contains
a default object (use DEFAULT-OBJECT? to test for it).

Additionally, HTTP requests have been changed so that the METHOD is a
string rather than a symbol (that is, "GET" rather than '|GET|).
v7/src/runtime/http-client.scm
v7/src/runtime/http-syntax.scm
v7/src/runtime/httpio.scm
v7/src/runtime/runtime.pkg