According to Geoff Hutchison:
> This poor piece of code. It's been wiped off my hard drive *twice*
> and languished in pieces for longer than it deserves. Have pity...
>
> I'd like some feedback on the current sorry state of the
> ExternalTransport class. I need to write up a Perl script as an
> example, probably as an https:// handler. I also need to patch
> htdig/Document.cc to check what protocols ExternalTransport can
> handle.
>
> Since it's coming horribly late, we need a vote on it. I obviously
> vote +1 conditional on me providing a useful example and making sure
> it works OK.
>
> I'll merge in Vadim's configuration changes (which were already
> approved) tomorrow afternoon. Then we'll certainly need to spend some
> significant time bug-hunting.
+1, with the same conditions you stated, and some docs of course
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.
--
Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba Phone: (204)789-3766
Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930
------------------------------------
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.
