At 12:06 PM -0600 11/15/99, Gilles Detillieux wrote:
>I'm curious, though, why you used single character record IDs, as for
>ExternalParser.cc, for things like content-type, etc., instead of using
>the same sort of headers used by HTTP. I guess it's not a problem except
>perhaps for the "c" content record, which will require the entire content
>on one line with no tabs, if I read the code correctly.
My initial thought was that it should approximate the ExternalParser
code. I realized the problem with "c" last night as I sat down to
code an example handler. Oops.
My other reasoning was that we should make the headers as
protocol-independent as possible. For example, one obvious
application is HTTPS, but FTP should be doable as well. It's easy to
make HTTP headers for HTTPS :-), but a bit more difficult for FTP.
I don't care either way, but I brought it up a few weeks ago and no
one seemed to care.
-Geoff
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.
