title: Creating and serving temporary HTML files in Azure
body: <p>We have an application that we would like to migrate to Azure for scale.  There is one place that concerns me before starting however:</p>
  
  <p>We have a web page that the user is directed to.  The code behind on the page goes out to the database and generates an HTML report.  The new HTML document is placed in a temporary file along with a bunch of charts and other images.  The user is then redirected to this new page.</p>
  
  <p>In Azure, we can never be sure that the user is going to be directed to the same machine for multiple reasons:  the Azure load balancer may push the user out to a different machine based on capacity, or the machine may be deprovisioned because of a problem, or whatever.</p>
  
  <p>Because these are only temporary files that get created and deleted <strong>very</strong> frequently I would optimally like to just point my application's temp directory to some kind of shared drive that all the web roles have read/write access to, and then be able to map a URL to this shared drive.   Is that possible? or is this going to be more complicated than I would like?</p>
  
  <p>I can still have every instance write to its own local temp directory as well.  It only takes a second or two to feed them so I'm ok with taking the risk of whether that instance goes down during that microsecond.  The question in this regard is whether the redirect to the temp HTML file is going to use http 1.1 and maintain the connection to that specific instance.</p>
  
  <p>thanks,
  jasen</p>