Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Windows Azure Blob Storage has the notion of a <a href="http://convective.wordpress.com/2010/01/20/access-control-for-azure-blobs/" rel="nofollow noreferrer">Shared Access Signature</a> (SAS) which could be issued on the server-side and is essentially a special URL that a client could write to without having direct access to the storage account API key. This is the only mechanism in Windows Azure Storage that allows writing data without access to the storage account key.</p> <p>A SAS can be expired (e.g., give user 10 minutes to use the SAS URL for an upload) and can be set up to allow for canceling access even after issue. Further, a SAS can be useful for time-limited read access (e.g., give user 1 day to watch this video).</p> <p>If your JavaScript client is also running in a browser, you may indeed have cross-domain issues. I have two thoughts - neither tested! One thought is <a href="http://en.wikipedia.org/wiki/JSONP" rel="nofollow noreferrer">JSONP</a>-style approach (though this will be limited to HTTP GET calls). The other (more promising) thought is to host the .js files in blob storage along with your data files so they are on same domain (hopefully making your web browser happy).</p> <p>The "real" solution might be Cross-Origin Resource Sharing (<a href="http://www.w3.org/TR/cors/" rel="nofollow noreferrer">CORS</a>) support, but that is not available in Windows Azure Blob Storage, and still emerging (along with other HTML 5 goodness) in browsers.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload