The way it's currently built, each ConcreteExporter will run it's own copy of the AbstractExporter.
This is inefficient and should be swapped out for a brand of the Strategy implementation which calls a single Explorer which calls the multiple sub-functions independently.
The way it's currently built, each
ConcreteExporter
will run it's own copy of theAbstractExporter
.This is inefficient and should be swapped out for a brand of the Strategy implementation which calls a single Explorer which calls the multiple sub-functions independently.