If the backend implementation used something like git's data store then
duplicate data would automatically be stored only once without any security
implications. The keys are the literal sha1 of the values. If two
websites had the same file tree containing the same files, it would be the
same
On Tue, Nov 5, 2013 at 11:45 AM, Tim Caswell t...@creationix.com wrote:
If the backend implementation used something like git's data store then
duplicate data would automatically be stored only once without any security
implications. The keys are the literal sha1 of the values. If two
On Wed, Nov 6, 2013 at 12:17 AM, Jonas Sicking jo...@sicking.cc wrote:
So unless webcompat at some point requiring it, I don't see us adding it.
See OP.
--
http://annevankesteren.nl/
I have seen the different bugs too, some comments:
- maybe I have missed some explaination or some obvious thing but I
don't understand very well right now the difference/use between
readable/writablebytestream and bytestream
- pause/unpause: as far as I understand the whatwg spec does not
On Nov 6, 2013 3:50 AM, Jonas Sicking jo...@sicking.cc wrote:
On Tue, Nov 5, 2013 at 11:45 AM, Tim Caswell t...@creationix.com wrote:
If the backend implementation used something like git's data store then
duplicate data would automatically be stored only once without any
security
Yes. I completely agree. Personally in my projects, I wish there was to
create custom filesystems backed by JavaScript code that are exported to
hierarchical URLs. It would work somewhat like server-side web development
where a js function handles the request for a file. This is basically
On Wed, Nov 6, 2013 at 8:46 AM, pira...@gmail.com pira...@gmail.com wrote:
Yes. I completely agree. Personally in my projects, I wish there was to
create custom filesystems backed by JavaScript code that are exported to
hierarchical URLs. It would work somewhat like server-side web
That's very interesting and useful, but I don't think it fits the same use
case I was talking about. I want the ability to create some object that
exports an URL that I can put in an iframe. Then all requests from that
iframe for resources will dynamically call my javascript code. I could
There are multiple interesting ideas being discussed
1. Mapping files to persistent URLs.
2. Sharing persistent URLs between different origins.
3. Using the ServiceWorker [1] to redirect URL requests (and possibly
manage it's own cache / files)
4. De-duping file copies using a Git like scheme.
On Wed, Nov 6, 2013 at 7:33 PM, Aymeric Vitte vitteayme...@gmail.comwrote:
I have seen the different bugs too, some comments:
- maybe I have missed some explaination or some obvious thing but I don't
understand very well right now the difference/use between
readable/writablebytestream and
On Wed, 06 Nov 2013 01:17:31 +0100, Jonas Sicking jo...@sicking.cc wrote:
window.screen.orientation seems like a better way forward.
Why would window.screen.orientation be any more correctly implemented than
window.orientation?
--
Simon Pieters
Opera Software
Because it will be portrait or landscale and not numbers like 0, 90, ...
which might start counting from portrait or landscape.
Kenneth
First off its unclear if they even have the same goal. Window.orientation
seems to have been interpreted as zero means default orientation rather
than zero means portrait. Unclear if that was the original intent or not.
Second, it seems less likely that someone will misunderstand portrait to
mean
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22059
Jianfeng Lin jianf...@microsoft.com changed:
What|Removed |Added
Status|RESOLVED|REOPENED
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22093
Jianfeng Lin jianf...@microsoft.com changed:
What|Removed |Added
Status|RESOLVED|REOPENED
15 matches
Mail list logo
