[Bug 17685] New: Hello, Please make the standard web socket api include a spec for an in browser "listener" socket. Meaning: a javascript application is able to create a server listener socket in the browser on the client. Another client can discover this ip (though most

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17685

           Summary: Hello, Please make the standard web socket api include
                    a spec for an in browser "listener" socket. Meaning: a
                    javascript application is able to create a server
                    listener socket in the browser on the client. Another
                    client can discover this ip (though most
           Product: WebAppsWG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#top
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: WebSocket API (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: contributor@whatwg.org
         QAContact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org


Specification: http://dev.w3.org/html5/websockets/
Multipage: http://www.whatwg.org/C#top
Complete: http://www.whatwg.org/c#top

Comment:
Hello,

Please make the standard web socket api include a spec for an in browser
"listener" socket.


Meaning: a javascript application is able to create a server listener socket
in the browser on the client.
Another client can discover this ip (though most likely a server provided
listing of some kind) and connect.
Perhaps include a spec for how this could interact with UPnP.


It is important to provide this feature, so as to help disrupt the current
"web server" -> "many client" industries that now exist.  
Disruption is a healthy process for technology.  Creating an environment where
new local minima can be found will increase the breadth and dynamism of our
technological landscape.  It will help destroy companies which in other
conditions might stay around and plague the system for far too long.

-------------------

I will give an example of how this simple addition could disrupt an entire
industry.
There are countless I can think of, but this may be the most shocking.


I wish to destroy google search:

1.  Client connects to my server, I give the 100 ips of known living clients.
2.  Client connects to remote remote client ip and requests the search.
3.  Remote client connects to google, searches, removes all ads, etc, etc.
4.  Remote client responds to local client with results.
5.  Local client displays results.  (during this time, the local client has
operated as a remote client for other clients.)

All of this happens quickly within the browser.
My server has become, basically, a router.  Very low cost, very low bandwidth.
 All via a server socket in browser.
My server's load would become less and less over time, as clients can remember
and resume.

-------------------

Please include disruptive technologies in your WebSocket specification.
Help us destroy the companies which exist today, to give room for the
companies of tomorrow.


Thanks,


Timothy Prepscius


Posted from: 98.14.81.235
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_4) AppleWebKit/534.57.2
(KHTML, like Gecko) Version/5.1.7 Safari/534.57.2

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

Received on Wednesday, 4 July 2012 01:28:07 UTC