Irv Salisbury III wrote:
It seemed like most of the readers would read the image into memory.
So, one thought on an enhancement might be to always read
the bytes in from the URL and then just hand that off instead
of opening the URL again.
Of course, this doesn't allow for future
Victor Mote wrote:
Irv Salisbury III wrote:
It seemed like most of the readers would read the image into memory.
So, one thought on an "enhancement" might be to always read
the bytes in from the URL and then just hand that off instead
of opening the URL again.
Of course,
Irv Salisbury III wrote:
I apologize if I came across as accusational.
No problem, I just thought I should supply some background.
I was trying to
understand the code so I knew the ramifications of creating a REST style
interface for my dynamically generated images. You have answered my
[EMAIL PROTECTED] wrote:
We have an api that generates a sort of barcode image that
needs to be put on the bottom of each page. However, each
image is unique and needs to be generated with some
information from the xml document. I know I can do this by
using a REST api call and putting
Quoting Victor Mote [EMAIL PROTECTED]:
[EMAIL PROTECTED] wrote:
We have an api that generates a sort of barcode image that
needs to be put on the bottom of each page. However, each
image is unique and needs to be generated with some
information from the xml document. I know I can
Quoting [EMAIL PROTECTED]:
Quoting Victor Mote [EMAIL PROTECTED]:
[EMAIL PROTECTED] wrote:
We have an api that generates a sort of barcode image that
needs to be put on the bottom of each page. However, each
image is unique and needs to be generated with some
information
[EMAIL PROTECTED] wrote:
While looking into this code, it looks like the FopImageFactory opens up a
stream to the image using the URL class, then the specific ImageReader
implementation reopens the stream again. So, if I did a REST style interface
to generate my images, it looks like it would be
J.Pietschmann wrote:
[EMAIL PROTECTED] wrote:
While looking into this code, it looks like the FopImageFactory opens
up a
stream to the image using the URL class, then the specific ImageReader
implementation reopens the stream again. So, if I did a REST style
interface
to generate my images, it
J.Pietschmann wrote:
The problem is that some stock image readers only accept a
stream with the pointer at the begin of the content, and if
the stream pointer can't be reset (e.g. if the analyser
needed so much info that the underlying implementation
already discarded buffers), then the
