Re: Polished FileSystem API proposal

2013-10-30 Thread pira...@gmail.com
+1 to symbolic links, they have almost the same functionality that hard links and are more secure and flexible (they are usually just plain text files...). El 30/10/2013 01:42, Brendan Eich bren...@mozilla.com escribió: Hard links are peculiar to Unix filesystems. Not interoperable across all

Re: Overlap between StreamReader and FileReader

2013-10-30 Thread Takeshi Yoshino
On Wed, Oct 23, 2013 at 11:42 PM, Aymeric Vitte vitteayme...@gmail.comwrote: Your filter idea seems to be equivalent to a createStream that I suggested some time ago (like node), what about: var encryptionPromise = crypto.subtle.encrypt(aesAlgorithmEncrypt, aesKey,

Re: Overlap between StreamReader and FileReader

2013-10-30 Thread Takeshi Yoshino
On Wed, Oct 30, 2013 at 8:14 PM, Takeshi Yoshino tyosh...@google.comwrote: On Wed, Oct 23, 2013 at 11:42 PM, Aymeric Vitte vitteayme...@gmail.comwrote: - pause: pause the stream, do not send eof Sorry, what will be paused? Output?

[xhr][xhr-1] status and plans

2013-10-30 Thread Jungkee Song
Hi, -Original Message- From: Arthur Barstow [mailto:art.bars...@nokia.com] Sent: Thursday, October 03, 2013 1:40 AM I am also interested in the status and plans for both the version of XHR that is supposed to move to LC-CR-REC in 2013 and the XHR-Bleeding-Edge version. As

[push-api]: Push API Patent Advisory Group (PAG) Recommends Continuing work on Push API Spec

2013-10-30 Thread Arthur Barstow
The Push API Patent Advisory Group published their `report` and it recommends WebApps continue to work on the spec http://www.w3.org/2013/10/push-api-pag-report.html. On 10/30/13 12:53 PM, ext Coralie Mercier wrote: The Push API Patent Advisory Group (PAG) [1] has published a report

Re: Polished FileSystem API proposal

2013-10-30 Thread Brian Stell
Good points! I was thinking of the logical functioning and hadn't considered the implementation. My understanding is that the UA will map from the filename to an actual file using some kind of database. My assumption was the logical idea of a link would happen in that layer. On Wed, Oct 30, 2013

FYI: Resource Priorities and Beacon API

2013-10-30 Thread Philippe Le Hegaret
FYI, the Web Performance Working Group just published Resource Priorities and Beacon yesterday and we're interested in feedback on the ideas and approaches. Resource priorities allows you to tweak the download priority of your resources, while Beacon enables synchronously transfer data from the

Re: Polished FileSystem API proposal

2013-10-30 Thread pira...@gmail.com
On most unix OSes, symbolic links are build using plain text files with just the path where they point inside and no more data, and later the OS identify them as a link instead a text file just by some special file flags, no more. On Windows, the direct access (.lnk) has a somewhat similar

RE: publish WD of Streams API; deadline Nov 3

2013-10-30 Thread Domenic Denicola
From: Arthur Barstow [mailto:art.bars...@nokia.com] If you have any comments or concerns about this proposal, please reply to this e-mail by November 3 at the latest. I have some concerns about this proposal, and do not think it is solving the problem at hand in an appropriate fashion. I

Re: FYI: Resource Priorities and Beacon API

2013-10-30 Thread Philippe Le Hegaret
On Wed, 2013-10-30 at 13:23 -0400, Philippe Le Hegaret wrote: FYI, the Web Performance Working Group just published Resource Priorities and Beacon yesterday and we're interested in feedback on the ideas and approaches. Resource priorities allows you to tweak the download priority of your

Re: CfC: publish WD of Streams API; deadline Nov 3

2013-10-30 Thread François REMY
| If you have any comments or concerns about this proposal, please reply | to this e-mail by November 3 at the latest. While adding streams to the platform seems a good idea to me, I've a few concern with this proposal. My biggest concerns are articulated over two issues: - Streams should

Re: Shadow DOM and Fallback contents for images

2013-10-30 Thread Ryosuke Niwa
On Oct 29, 2013, at 6:04 PM, Boris Zbarsky bzbar...@mit.edu wrote: On 10/14/13 12:11 AM, Ryosuke Niwa wrote: If I'm not mistaken, how alternative text is presented is up to UA vendors. You're mistaken. The HTML spec actually defines the behavior here, in standards mode: it's presented as

Re: Shadow DOM and Fallback contents for images

2013-10-30 Thread Boris Zbarsky
On 10/30/13 5:56 PM, Ryosuke Niwa wrote: Interesting. Could you point me to the part of the spec. that mandates this behavior? http://www.whatwg.org/specs/web-apps/current-work/multipage/rendering.html#images-0 says: When an img element represents some text and the user agent does not

[Bug 23479] File Constructor and Blob Constructor should have same signature

2013-10-30 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23479 Arun a...@mozilla.com changed: What|Removed |Added Status|NEW |RESOLVED

Re: publish WD of Streams API; deadline Nov 3

2013-10-30 Thread Aymeric Vitte
As you mention streams are existing since the begining of times and it's incredible that this does not exist on a web platform, but apparently the subject is still not so easy, node changed its stream quite a lot of time. I probably will not be able to answer back in the coming days but your

Re: Polished FileSystem API proposal

2013-10-30 Thread pira...@gmail.com
What you are asking for could be fixed with redirects, that it's the HTTP equivalent of filesystems symbolic links :-) 2013/10/31 Brian Stell bst...@google.com: In Request for feedback: Filesystem API [1] it says This filesystem would be origin-specific. This post discusses limited readonly

Re: CfC: publish WD of Streams API; deadline Nov 3

2013-10-30 Thread Dean Landolt
I really like this general concepts of this proposal, but I'm confused by what seems like an unnecessary limiting assumption: why assume all streams are byte streams? This is a mistake node recently made in its streams refactor that has led to an objectMode and added cruft. Forgive me if this has

Splitting Stream into InputStream and OutputStream (was Re: CfC: publish WD of Streams API; deadline Nov 3)

2013-10-30 Thread Takeshi Yoshino
Hi François On Thu, Oct 31, 2013 at 6:16 AM, François REMY francois.remy@outlook.com wrote: - Streams should exist in at least two fashions: InputStream and OutputStream. Both of them serve different purposes and, while some stream may actually be both, this remains an exceptional

Defining generic Stream than considering only bytes (Re: CfC: publish WD of Streams API; deadline Nov 3)

2013-10-30 Thread Takeshi Yoshino
Hi Dean, On Thu, Oct 31, 2013 at 11:30 AM, Dean Landolt d...@deanlandolt.com wrote: I really like this general concepts of this proposal, but I'm confused by what seems like an unnecessary limiting assumption: why assume all streams are byte streams? This is a mistake node recently made in