Open tevert opened 8 years ago
Are we using our existing backend or rewriting for this? I can work on pulling the back-end part into its own library with the tests.
we might need to rethink how file i/o works with the web app, too.
I also think that epics are useless in this format and we should probably try and create a smaller list of tasks to keep open
Regarding tasks vs. epics - lets discuss that elsewhere so as not to clutter this issue too much.
My thought is yes - pull MediaComplete.Lib into it's own solution, which should already be relatively straighforward, and stick a web API on top of it.
In terms of file IO, I agree that handling remote files is a potential nightmare, so for our first pass I recommend having all API endpoints accept string paths to files as arguments, and have audio simply come from the server's speakers. An MVP would be something that's essentially just running in the background supporting the Electron app.
Does that make sense?
Yep
Create a web API for Media Complete functionality. This includes library/file manipulation, audio streaming, etc.