- From: Michael Saunders <michael@amtec.com>
- Date: Wed, 06 Oct 1999 11:28:08 -0700
- To: www-lib@w3.org
Hello, I am using libwww's HTTP upload capability via a call to HTPutDocumentAnchor. I noticed that for very large files I was running out of space in my temporary directory. I traced it down to a portion of code in the HTConverterInit function where the HTSaveLocally converter is being registered with the HTMIME module (this is not the problem area but it gets it ready for the problem later on). Eventually, during the HTTP upload, LibWWW works its way around to calling the pumpData function in the HTMIME module. This function's comments indicate that when it can not determine the content type it calls it's registered "me->save_stream" function -in this case HTSaveLocally which was registered in the HTConverterInit function. Questions: 1) Does the content get translated to some other format when the stream is saved to a local file? 2) Why must it save the stream to local file when the stream already came from a local file? 3) If no translation is necessary doesn't LibWWW provide a converter that effectively passes along the data unmodified? 4) Why doesn't LibWWW recognize the content type in the first place as I previously bound my file extension by a call to HTBind_add. 5) Any recommendations to avoid the temporary file created by LibWWW? Thanks, Michael
Received on Wednesday, 6 October 1999 14:28:29 UTC