On Mon, Nov 29, 2010 at 11:45 AM, Joran Greef wrote:
> I have some questions regarding the FileSystem API:
>
> 1. It would be great to be able to let the user choose where they want their
> sandboxed directory located for the web app, i.e. on the desktop for quick
> access. That way they can dra
When we started studying the subject we looked at multiple different
addressing and routing options. We had discussions with some HIP and
PSIRP researchers about their experiences with related problems. At
some point we considered designing a separate overlay that would
connect browsers. In the end
Hi Toni,
Any notes or thoughts on the DNS and IP Routing side of things, as in
how to distinguish between the various listening browsers on my private
network which all share a single public IP address, and also how to
negate conflicts + expose the details of the listening socket to the
user
Hello,
I work for the computer science department at the University of
Helsinki, Finland. We've been trying to define an API that would allow
web site developers to run simple servers in their web pages. The
motivation behind the research is establishing some ground for
browser-to-browser networki
On Mon, 29 Nov 2010 18:21:44 +0100, Anne van Kesteren
wrote:
Before I write it out it would be nice to assess whether there is
consensus on this. From the current draft, asBlob, responseBlob, and
responseArrayBuffer are removed. response and responseType are added.
http://dev.w3.org/2006/w
On Tue, 30 Nov 2010 15:53:01 +0100, Arthur Barstow
wrote:
Hi Anne - since this CfC was started, there were three threads on this
spec:
1. [ProgressEvents] How to deal with compressed transfer encodings Jonas
Sicking
http://lists.w3.org/Archives/Public/public-webapps/2010OctDec/0757.html
2.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11439
Summary: Extend ProgressEvent with position and totalSize
attributes
Product: WebAppsWG
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Se