I know of some workarounds available (using remote proxy for HTTP encapsulation, using browser plug-ins), but these will not use the browser’s cache (usually the system cache), or need Potentially unwelcome dependencies on users. Customers.
I have read a reasonable amount of information about the security aspects of the issue, but none of them really convinced me. Is it just that no one is in WHATWG / W3C recommends and releases specifications, or is there a real reason to oppose such an API?
Related questions:
> DNS resolver libraries with support for DNSSEC and/or experimental new RR types
> Determine IP# of domain from client browser
> Javascript – Simple – getting an Ip from a URL
> Perform a DNS lookup to resolve a hostname to an IP address using JavaScript
> http://lists.w3.org/Archives/Public/public-webapps/ 2011AprJun/1065.html
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=12965
This was discussed in May 2011. I did not I found any other content on other related lists, nor did I find any other content on WHATWG, so I now assume that this is the current state (as of July 2013).
To summarize:
>There are reasonable concerns,
>It is not clear that they cannot overcome it,
>has not yet submitted a formal proposal to W3C or WHATWG,
>may need the support of the browser vendor first, because the Function seems to be very important,
>needs a set of use cases.
PS: I also retrieved the logs for the discussion at #whatwg on Freenode mentioned in the bug entry; it does not seem to be direct Related (although I did scan this quickly).
Edit: Oh, about the potential uses of WebSockets; it still doesn’t make use of browser/system caching, you still need a proxy server for the WebSockets HTTP handshake .
Update: The sysapps working group is writing a specification for the appropriate raw socket API, which will support both UDP and TCP.
We Is it reasonable to expect the API to access the browser’s own DNS resolver? If not, why?
I know of some workarounds available (using remote proxy for HTTP encapsulation, using browser plug-ins), but these will not use the browser’s cache (usually the system cache), or need Potentially unwelcome dependencies on users. Customers.
I have read a reasonable amount of information about the security aspects of the issue, but none of them really convinced me. Is it just that no one is in WHATWG / W3C recommends and releases specifications, or is there a real reason to oppose such an API?
Related questions:
> DNS resolver libraries with support for DNSSEC and/or experimental new RR types
> Determine IP# of domain from client browser
> Javascript – Simple – getting an Ip from a URL
> Perform a DNS lookup to resolve a hostname to an IP address using JavaScript
The second place on the W3C list (Right now) for mining.
> http://lists.w3.org/Archives/Public/public-webapps/2011AprJun/1065.html
> https:/ /www.w3.org/Bugs/Public/show_bug.cgi?id=12965
This was discussed in May 2011. I did not find anything else on other related lists, nor did I I found anything else on WHATWG, so I’m assuming this is the current state (as of July 2013).
To summarize:
>There are reasonable concerns,
> It is not clear that they cannot be overcome,
>has not yet submitted a formal proposal to W3C or WHATWG,
>may need the support of the browser vendor first, because the feature seems to be very important,
>requires a group Use case.
PS: I also retrieved the logs for the discussion at #whatwg on Freeenode mentioned in the bug entry; it does not seem to be directly related (though I did scan this soon).
Edit: Oh, about the potential uses of WebSockets; it still doesn’t make use of browser/system cache, you still need a proxy server for WebSockets HTTP handshake.
Update: sysapps working The group is writing a specification for the appropriate raw socket API, which will support both UDP and TCP.