Have Sockets Run Their Course?
ChelleChelle writes "This article examines the limitations of the sockets API. The Internet and the networking world in general have changed in very significant ways since the sockets API was first developed in 1982, but the API has had the effect of narrowing the ways in which developers think about and write networked applications. This article discusses the history as well as the future of the sockets API, focusing on how 'high bandwidth, low latency, and multihoming are driving the development of new alternatives.'"
I think sockets work fi.... *connection lost, host not routable*
Well, I did hear it was a Xerox standard so it must have been copied from someone. I guess it could have been Apple.
"Well, I did hear it was a Xerox standard so it must have been copied from someone."
I hope you meant to make that joke.
http://www.rootstrikers.org/
Or more like this? :)
Rampant carbon sequestration destroyed the Dinosaurs' tropical paradise. I'm here to help repair the damage.
My socks are fine for now. When they do run their course I go to walmart and get new socks its $5 for 6 pair!
alt.news.slashdot?
Firewalls don't support [SCTP]. Consumer routers can't do NAT on it. New protocols on the Internet are fairly unlikely to have a chance.
This is a good example of why NAT sucks. When IPv6 comes along and and restores true end-to-end connectivity across the Internet, there will be a lot more freedom to experiment with new and interesting protocols. Except, of course...
New protocols on the Internet are fairly unlikely to have a chance.
Damn.
You mean, like pipes?
Pipes for local communication and tubes for global communication. Seems like a winner.
Sorry to cut it to you, but NAT is here to stay. As a security paradigm, there's no surface attack to a user's PC that isn't even visible.
Bye!