We've historically had the verifier always running and pinging the tracks table for new tracks, this new implementation expects to be called by a cronjob or similar. But we might also want to step away from that and have the song acception code call into the verifier instead with a filename argument so we could potentially stop before it even gets accepted completely.
Not sure what is the most feasible/best thing to do here, opinions @Bevinsky ?
We've historically had the verifier always running and pinging the tracks table for new tracks, this new implementation expects to be called by a cronjob or similar. But we might also want to step away from that and have the song acception code call into the verifier instead with a filename argument so we could potentially stop before it even gets accepted completely.
Not sure what is the most feasible/best thing to do here, opinions @Bevinsky ?