Thanks for the thought-provoking point. I suppose that it should be perfectly fine to ony use set-size to grow a file in concert with a successful RIA request.
--Scott On Dec 30, 2009 10:07 AM, <[email protected]> wrote: Send pdf-devel mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit http://lists.gnu.org/mailman/listinfo/pdf-devel or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of pdf-devel digest..." Today's Topics: 1. Re: RFC on fsys-http design (James Cloos) 2. Re: Doubt about pdf_alloc (Luca Braglia) ---------------------------------------------------------------------- Message: 1 Date: Tue, 29 Dec 2009 18:11:00 -0500 From: James Cloos <[email protected]> Subject: Re: [pdf-devel] RFC on fsys-http design To: [email protected] Cc: Scott Fohey <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset=us-ascii >>>>> "Scott" == Scott Fohey <[email protected]> writes: Scott> It will require setting the size of the temp file to the full Scott> size of the to-be-downloaded item right from the start, [Just to play devil's advocate...] How do you intend to deal with pdf files from servers which do not know/ advertise the pdf's size even if they advertize byte-range support? A number of bug sites and other cms frameworks fail to send a Content- Lenght header when, eg, grabbing attached files. I do not know how often Accept-Ranges is there, but Content-Lenght is not, so it might not matter. But just in case..... -JimC -- James Cloos <[email protected]> OpenPGP: 1024D/ED7DAEA6 ------------------------------ Message: 2 Date: Wed, 30 Dec 2009 11:53:37 +0100 From: Luca Braglia <[email protected]> Subject: [pdf-devel] Re: Doubt about pdf_alloc To: Gnu PDF Developers <[email protected]> Message-ID: <20091230105337.ga2...@a6k> Content-Type: text/plain; charset=utf-8 On 29/12/09 - 15:31, Luca Braglia wrote: > might it be > > if (pointer && size == 0) or if (pointer && !size){...} > { > pointer = NULL; > } > > so that pdf_alloc handles this exception (if one ask for 0 heap > bytes) unlike classic malloc (that returns a pointer)? at least on my Debian... a rationale could be to uniform return value from malloc(0) across platforms (from current draft standard - 7.20.3): If the size of the space requested is zero, the behavior is implementation- defined: either a null pointer is returned, or the behavior is as if the size were some nonzero value, except that the returned pointer shall not be used to access an object. if i missed something, please let me know bye End of pdf-devel Digest, Vol 30, Issue 18 *****************************************
