On Wed, Aug 5, 2009 at 8:08 PM, Garrett Smith wrote:
> On Wed, Aug 5, 2009 at 1:04 AM, Arun Ranganathan wrote:
> > Garrett Smith wrote:
> >>
> >> Please show the subsequent use cases you've studied and please do
> >> publish your studies.
> >>
> >>
> >
> > What I meant by "use cases" was this exch
On Aug 5, 2009, at 9:42 PM, Jonas Sicking wrote:
2009/8/1 João Eiras :
How can one in a script check for UA support?
else if(localStorage){}
does not work for Opera**.
This obviously does not work because you need to prefix
localStorage with window "if(window.localStorage)" else the scr
2009/8/1 João Eiras :
>>
>>
>> How can one in a script check for UA support?
>> else if(localStorage){}
>> does not work for Opera**.
>
> Hi.
> This obviously does not work because you need to prefix localStorage with
> window "if(window.localStorage)" else the script breaks because localStorage
>
On Wed, Aug 5, 2009 at 1:04 AM, Arun Ranganathan wrote:
> Garrett Smith wrote:
>>
>> Please show the subsequent use cases you've studied and please do
>> publish your studies.
>>
>>
>
> What I meant by "use cases" was this exchange:
>
> http://lists.w3.org/Archives/Public/public-webapps/2009JulSep/
A few comments:
Need to specify that all getAsX functions call the callback
*asynchronously*. Also need to integrate this with the HTML5 event
loop.
getAsBinary should be called getAsBinaryString so that once we have a
BinaryArray or some such we can add a getAsBinary that truly returns
binary da
Oh, getAsURL should also be synchronous since no IO is occurring.
/ Jonas
On Wed, Aug 5, 2009 at 6:55 PM, Jonas Sicking wrote:
> A few comments:
>
> Need to specify that all getAsX functions call the callback
> *asynchronously*. Also need to integrate this with the HTML5 event
> loop.
>
> getAsBi
How about this?
Why make a new API for getting the contents of a file (local or otherwise)
when we already have one which is XHR?
What if FileList was just array of File objects where each File object is
just a URL in the format
"filedata: uuid, filename"
Then you can use that URL anywhere in H
Hi,
the spec lists a use case about a web app that needs to send file(s) to the
server programmatically. I happen to think lately about an E-mail app that
can send attachments. FileData and its splice() method are useful here. I
assume the XHR2 spec would get XHR.send(FileData) method. XHR2 provid
Gregg Tavares wrote
The File API is meant to talk to your local file system. It isn't a
"network download" API, but it seems that's what you want :-). Perhaps I am
misunderstanding your question?
Sorry, I was told on the HTML5 list that this is where network downloads and
archive suppor
Dmitry,
the spec lists a use case about a web app that needs to send file(s) to the
server programmatically. I happen to think lately about an E-mail app that
can send attachments. FileData and its splice() method are useful here. I
assume the XHR2 spec would get XHR.send(FileData) method. XHR2
Informative references include RFC 2818. Please also include RFC2817,
as it's preferable on architectural grounds (the https scheme is
believed to be a mistake because it has semantics equivalent to http).
This would be a very useful exercise being that many devices are now
shipping with or at least browser capable.
Some examples:
- sony playstation portable
- nintendo ds: http://en.wikipedia.org/wiki/Nintendo_DS_Browser
- Garmin GPS: http://www8.garmin.com/products/communicator/
2009/8/4 ~:'' あり
On Wed, 05 Aug 2009 10:59:46 +0200, Gregg Tavares wrote:
Sorry, I was told on the HTML5 list that this is where network downloads
and archive support stuff belonged.
It certain seems like a good fit to me.
That is true, but it seems you conflate networking with files. Networking
is the do
On Wed, 05 Aug 2009 10:04:28 +0200, Arun Ranganathan
wrote:
In the case of file read APIs, simply getting the data asynchronously is
more convenient than using events. There is no intrigue at work here,
merely disagreement.
I could imagine that for reading data you might want to have even
>
> HTTP Pipelining What specification changes do you propose? Something
> normative, or just more explanatory stuff?
Actually I don't have a specific proposal for HTTP pipelining because I
think that it's going to be more difficult to implement since it would
involve changes to the HTTP protocol
On Tue, Aug 4, 2009 at 12:15 PM, Sebastian Markbåge
wrote:
> There has been some talk about supporting packages/archives in web APIs.
>
> http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-July/021586.html
> http://lists.w3.org/Archives/Public/public-webapps/2009JulSep/0460.html
>
>
On Wed, Aug 5, 2009 at 1:47 AM, Arun Ranganathan wrote:
> Gregg Tavares wrote:
>
>> I'd really like to contribute to this as I'm helping implement WebGL and
>> we
>> need a way to get LOTS of data into WebGL. Hundreds of files per app.
>>
>> That said, there's a bunch of things I don't understand
Gregg Tavares wrote:
I'd really like to contribute to this as I'm helping implement WebGL and we
need a way to get LOTS of data into WebGL. Hundreds of files per app.
That said, there's a bunch of things I don't understand about the API
*) Given that XMLHttpRequest is limited to a same domain p
I'd really like to contribute to this as I'm helping implement WebGL and we
need a way to get LOTS of data into WebGL. Hundreds of files per app.
That said, there's a bunch of things I don't understand about the API
*) Given that XMLHttpRequest is limited to a same domain policy but the img
tag,
Garrett Smith wrote:
Please show the subsequent use cases you've studied and please do
publish your studies.
What I meant by "use cases" was this exchange:
http://lists.w3.org/Archives/Public/public-webapps/2009JulSep/0371.html
http://lists.w3.org/Archives/Public/public-webapps/2009JulSep/
On Tue, Aug 4, 2009 at 6:55 PM, Arun Ranganathan wrote:
> I have updated the draft of the File API, and welcome more review. Note
> that it is no longer called "FileUpload" since this term has become
> misleading.
>
> In particular, here are some of the issues addressed (and some not):
>
>> Any re
21 matches
Mail list logo
