Inject genscrape and listen for all events (AJAX trees could fire multiple events as the user browses)
Inject genscrape, wait for one event, then tear down
genscrape supports usecase (1) right now but doesn't support (2).
Should we add a configuration option that only allows one event to be fired or should we add a destroy() method that apps are expected to call when they want usecase (2)? Perhaps both.
This issue is irrelevant if we commit to #75 because that kills usecase 1 from above and leads to usage where scrapers are expected to clean up when necessary after running.
There are two general usecases:
genscrape supports usecase (1) right now but doesn't support (2).
Should we add a configuration option that only allows one event to be fired or should we add a destroy() method that apps are expected to call when they want usecase (2)? Perhaps both.