I change my opinion. In the access control spec, I now see:
5.1 Simple Cross-Origin Request, Actual Request, and Redirects
In response to a simple cross-origin request or actual request the
resource indicates whether or not to share the response.
If the resource has been relocated, it indicates
On Sun, 16 Aug 2009 10:00:08 +0200, Aaron Boodman a...@google.com wrote:
I change my opinion. In the access control spec, I now see:
5.1 Simple Cross-Origin Request, Actual Request, and Redirects
In response to a simple cross-origin request or actual request the
resource indicates whether or
On Wed, 12 Aug 2009, Aaron Boodman wrote:
I also don't see what not having a callback buys. I'm not sure if you
noticed, but I was suggesting that the callback be reentrant. So if you
do this:
var theResult = null;
database.syncTransaction(function(tx) {
theResult =
Currently we have File and FileData, where a File object ISA FileData
object... completion is delivered via readXXX method completion callbacks.
It would be easy to add progress callbacks to those readXXX methods.
I think Garrets point about two different corners of the webapp issuing
reads
On Sat, Aug 15, 2009 at 9:19 AM, Garrett Smithdhtmlkitc...@gmail.com wrote:
On Tue, Aug 11, 2009 at 7:20 PM, Jonas Sickingjo...@sicking.cc wrote:
Here is an alternative proposal for an API for reading files:
[snip proposal]
As stated, I'm not convinced that this is a better solution than
