refactor archiving implementation to be more seamless
Closed this issue · 1 comments
aoberoi commented
the current archiving implementation is built as a functional "extension" of the OpenTok object definition. it would be nice to clean this up to make the code less repetitive and harmonious. this also includes the jasmine based tests (which contrast with the other mocha based tests).
it would be favorable to keep the implementation of archiving decoupled. one possible solution is to export a "mix-in" function from lib/archiving.js that could be used to extend OpenTok.prototype.
michaeljolley commented
Closing as outdated.