Future Library
Closed this issue · 1 comments
andrewvy commented
After this basic API abstraction for wrapping the chrome-remote-interface
, I'd like to tackle a new library that builds on top of these foundations.
- GenStage for funneling jobs to chrome headless workers
- Multiple chrome headless instances (Not sure if this is necessary if we have multiple pages)
- Distributed chrome headless job processing?
And naming a library is hard. Something about managing groups of "headless workers"..
andrewvy commented
Higher-level management library will be developed at: andrewvy/chromesmith.