Tag Info

New answers tagged

1

Your first approach looks much cleaner than the second, but I do not think you have to sacrifice performance necessarily by choosing this design. Assumed it turns out the approach is really not efficient enough, then you could use your PDFDocument as an abstraction over your preferred pdf representation "behind the scenes". What you call a PDFDocument, does ...


4

I sounds like you're trying to create an adapter around a third party library to avoid it becoming coupled in your business logic. Out of the two approaches you mention, the first one seems the best idea, as it's the most flexible and you can separate your business logic from the adapter (i.e. the adapter will basically be a pass through to the third party ...



Top 50 recent answers are included