title: Protect remote resources when served with nodejs
body: <p>This is more of an architecture question involving nodejs as implementation.</p>
  
  <p>I have on a folder not exposed by the webserver files that I want to offer to the user.</p>
  
  <p>The way nodejs should expose the resource to the end user is via a one shot link, that once is consumed is no longer available.
  The user through the entire experience should never know the real location of the file.</p>
  
  <p>I'm sure this is a common architecture pattern, but I have never implemented something similar.
  Looking at scalability, the resource shouldn't be copy either on HD or RAM, and if possible the solution should not relay on a DB token tracking system.</p>
  
  <p>I don't necessary need a code implementation, but a detail explanation on how I should implement it</p>
  
  <p>Thank you so much</p>