Whither Sockets? - ACM Queue
http://queue.acm.org/detail.cfm?id=1538949

The Internet and the networking world in general have changed in very significant ways since the sockets API was first developed, but in many ways the API has had the effect of narrowing the way in which developers think about and write networked applications. This article begins by briefly examining some of the conditions present when the sockets API was developed and considers how those conditions shaped the way in which networking code was written. The remainder of the article looks at ways in which developers have tried to get around some of the inherent limitations in the API and talks about the future of sockets in a changing networked world.

"High bandwidth, low latency, and multihoming challenge the sockets API." (via @gnat) Especially true when people like Michael Nygard say things like "I prefer my servers to have a minimum of 4 NICs, preferably 6".

Are you planning to use your notebook abroad? If yes, you may want to check what type of power plugs and sockets are used in the part of the world you are travelling to. All EUROCOM Notebooks come with AC adapters switching between 110V and 240V allowing the notebooks to be used all over the world. However, you may not be able to use the US/Canadian power plug overseas. Please check what type of power plug and socket is used in a country of your destination. You may want to buy a foreign plug in your local electronics store before you travel abroad.

""les prises electriques dans le monde"

Check what type of power plug and socket is used in a country of your destination. You may want to buy a foreign plug in your local electronics store before you travel abroad.

Simple preforking echo server in Python. Python port of http://tomayko.com/writings/unicorn-is-unix.

Web Sockets Now Available In Google Chrome

The Web Sockets API enables web applications to handle bidirectional communications with server-side process in a straightforward way.

When will this be usable?

"Starting in the Google Chrome developer channel release 4.0.249.0, Web Sockets are available and enabled by default. Web Sockets are "TCP for the Web," a next-generation bidirectional communication technology for web applications being standardized in part of Web Applications 1.0."

Chrome set to take over the world

The Web Sockets API enables web applications to handle bidirectional communications with server-side process in a straightforward way. Developers have been using XMLHttpRequest ("XHR") for such purposes, but XHR makes developing web applications that communicate back and forth to the server unnecessarily complex. XHR is basically asynchronous HTTP, and because you need to use a tricky technique like long-hanging GET for sending data from the server to the browser, simple tasks rapidly become complex. As opposed to XMLHttpRequest, Web Sockets provide a real bidirectional communication channel in your browser. Once you get a Web Socket connection, you can send data from browser to server by calling a send() method, and receive data from server to browser by an onmessage event handler.

"After a small amount of experimentation I was able to make Erlang talk to a web page using pure asynchronous message passing. I think this means the death of the following technologies: comet long-poll AJAX keep-alive sockets"

Erlang's creator anoints websockets (includes example server and client)

After a small amount of experimentation I was able to make Erlang talk to a web page using pure asynchronous message passing.