Leonard Rosenthol wrote: > Then I would put some debugging code into iText to time how much of the > getInstance() method is spend in actually reading the image from the server > vs. the rest of the machinery in there. That will give you an obvious > indication of whether the bottleneck is iText or I/O. > > Once you know that - then you can start looking for solutions...Otherwise, > you're just guessing.
One of the known problems is that iText fetches the first bytes of the image first to determine the image type. Once the image type is known, it fetches the complete image. While this is OK for some InputStreams, it costs when a connection needs to be made. Therefore it's better to download the image bytes first, and use those bytes to create the Image object. -- This answer is provided by 1T3XT BVBA http://www.1t3xt.com/ - http://www.1t3xt.info ------------------------------------------------------------------------------ _______________________________________________ iText-questions mailing list iText-questions@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/itext-questions Buy the iText book: http://www.itextpdf.com/book/ Check the site with examples before you ask questions: http://www.1t3xt.info/examples/ You can also search the keywords list: http://1t3xt.info/tutorials/keywords/
