Aug 30, 2017 04:05 PM|mgebhard|LINK
I did try to debug it and it does go through the deleting and recreating the file but for some reason it still plays the previous wav file and not the new one.
As far as I can tell, this design will not work for more than one user. You'll need to buffer audio request in memory. For example, if the wave.wav is not buffered, get wave.wav from the DB and add it to an in memory dictionary. If wave.wav is found in
memory, return the buffered content or perhaps stream the content.
IMHO, it would be far easier to store the audio files on disk and use the database to relate the audio files to the users.