http headers and stream-element-type
From: Sam Steingold (sds_at_gnu.org)
Date: 01/26/05
- Next message: Marco Parrone: "Re: Lisps' popularity"
- Previous message: Drew Krause: "Re: 'On Lisp' for $140"
- Next in thread: Edi Weitz: "Re: http headers and stream-element-type"
- Reply: Edi Weitz: "Re: http headers and stream-element-type"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 26 Jan 2005 13:05:25 -0500
the HTTP response to a "GET foo" request consists of headers, blank
line, and data.
it is preferable to parse headers as text (STREAM-ELEMENT-TYPE =
CHARACTER) but sometimes one wants to process data as binary
(STREAM-ELEMENT-TYPE = (UNSIGNED-BYTE 8)).
ACL permits interchangeable READ-LINE and READ-SEQUENCE into a byte
vector on the socket stream.
CLISP has (SETF STREAM-ELEMENT-TYPE).
How about CMUCL, ABCL, LW, MCL &c?
What do you do if you want to mix binary and character i/o on the same
stream?
Thanks.
-- Sam Steingold (http://www.podval.org/~sds) running w2k <http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/> <http://www.mideasttruth.com/> <http://www.honestreporting.com> Two wrongs don't make a right, but three rights make a left.
- Next message: Marco Parrone: "Re: Lisps' popularity"
- Previous message: Drew Krause: "Re: 'On Lisp' for $140"
- Next in thread: Edi Weitz: "Re: http headers and stream-element-type"
- Reply: Edi Weitz: "Re: http headers and stream-element-type"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]