I am working through the implementation details of making PDFStreamEngine a
singleton.

I would like to do so because I need for the PDXObjectImage to be able to
get the current nonstroking colorspace.

The call
*CS =
PDFStreamEngine.getInstance().getGraphicsState().getNonStrokingColorSpace();
*
would solve this very nicely.

My understanding is that there is really only one PDFStreamEngine (or
descendant thereof) in existence (within a particular thread's context)
anyway.

Does anyone see a problem with making PDFStreamEngine a singleton?  A big
theoretical problem, a reason it should not be attempted?

I think I can work through the implementation details, as I said.  And I
will certainly run the junit tests to make sure the thing behaves in all our
defined scenarios.

Thanks!

Daniel Wilson

Reply via email to