linuxunil, linuxunil wrote > First, read the PDF format specification v1.7, section 3.4.5 page 98 > http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/pdf_reference_1-7.pdf > Talks about "Incremental Updates." Read this section for more info of what > I'm talking here.
Please use the ISO PDF specification (which also is publicly available on the Adobe site: http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/PDF32000_2008.pdf); by using RFC style lingo, some details are more accurate in the ISO spec than in the Adobe spec. Furthermore it is the (current) standard concerning the PDF format. > I edited my previous posts to make it clear. Editing your posts is futile for mailing lists mirrored on nabble as the edits aren't forwarded to the mailing list. nabble does show a banner "Your changes will not be sent to the mailing list. If you want others in the mailing list to know of your changes, please compose a new message or reply to your original message." when you edit your posts which is quite to the point. > InputStream revisionIs = revisionFields.extractRevision("Sig1"); //<-- > revision is supposed to be here > > System.out.println("#> INPUTSTREAM AVAIBLE COUNT : " + > revisionIs.available()); > > byte[] revisionBuffer = new byte[revisionIs.available()]; > revisionIs.read(revisionBuffer); > revisionIs.close(); > System.out.println("##> REVISION SIZE " + revisionBuffer.length); What makes you think this could work at all? InputStream.available() only in very special InputStream implementations returns the length of the complete data to retrieve from the stream, FileInputStreams coming to my mind. Generally it's merely "an *estimate* of the number of bytes that can be read (or skipped over) from this input stream *without blocking*" (cf the InputStream JavaDocs). > If is the second (or later) that file is requested, the file to be sent to > the client will be the last appended update. Even if you correctly read the revision input stream, that would not be what you want as it is not merely the data added during the associated incremental update but all data up to and including that incremental update, excluding anything newer. You actually merely want an end piece of that. As you know the size of the data you had before, you know how long a head piece you have to skip. Regards, Michael -- View this message in context: http://itext-general.2136553.n4.nabble.com/Pdf-Incremental-Updates-tp4659069p4659098.html Sent from the iText - General mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk _______________________________________________ iText-questions mailing list iText-questions@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/itext-questions iText(R) is a registered trademark of 1T3XT BVBA. Many questions posted to this list can (and will) be answered with a reference to the iText book: http://www.itextpdf.com/book/ Please check the keywords list before you ask for examples: http://itextpdf.com/themes/keywords.php
