OK, I still need to write the documentation (yes, I know I'm horrible). But I just committed the changes to support ExternalTransport scripts, essentially the code I posted earlier, but this time I've tested it and changed the syntax somewhat. Rather than messing with the contents any, there's a header section, followed by a blank line, followed by the content--this roughly matches Gilles suggestions, as well as HTTP. ;-) How much has it been tested? I wanted to try it on HTTPS, but I still need to compile an HTTPS-enabled version of curl. If someone knows of another similar program, I'll try that. My ultimate aim is that I'll use the Perl LWP for a handler that can do HTTP, HTTPS, and FTP. I didn't write the documentation because I wanted to allow people to suggest changed syntax, etc. BTW, in the process, I discovered a gross inefficiency in the current ExternalParser/ExternalTransport code. Each time one of these is used, the Document class kills off the previous incarnation, then makes a new one. It would probably be a lot cleaner if the class just picked the appropriate command line in either Parse() or Retrieve(). Seem reasonable? -Geoff ------------------------------------ To unsubscribe from the htdig3-dev mailing list, send a message to [EMAIL PROTECTED] You will receive a message to confirm this.
