New API’s for your browser permit real-time browser-to-browser communication

Author	Message
	Posted: Mon May 09, 2011 15:26 Author: sam_code4u Our current Internet requires web servers to host websites. But this will be changing soon. The World Wide Web Consortium (W3C – yeah those folks with the free tutorials on web programming) have developed a new working group focused on real time Application Programming Interfaces (APIs) that allow web browsers to connect directly to one another, in real time! How is this awesome? Because instead of your browser communicating with a server it can just talk with another computer’s browser, for anything, from video to chatting and even (gulp) filesharing. Another benefit, outlined here, is that the bypassing of centralized servers removes the control certain groups, corporations, organizations, and governments are trying to enforce. Technically, your packets still have to flow across their networks, but these new API’s are being designed to avoid server-side implementation. It’s similar to Opera’s Unite, but instead of being just with Opera, it would be a defined standard so ANYONE can do it. Yes, that means when the US government decides filesharing is causing devastation to music/movies/software companies and requires web browsers to disable these API’s, new ones (and there are always new ones) will pop up and they’ll know how to follow the standard. Rest assured there should be plugins to prevent snooping as we all know some like to do that. So what is it? Well… you know how your browser allows embedding applications, like Adobe’s flash or Apple’s Quicktime? Well now the API’s will allow any application to work, no plug-ins, or central server to store the data to share (ie: no Napster servers required). For example, P2P API’s exist in Chromium. That’s right, you can fileshare without using Limewire or whatever your flavour is for filesharing application. Better yet, wait for the BitTorrent to be built right in. Google is part of this as is Ericsson, but it’s not all bad, as long as you have the source, you can cut-out anything you don’t like and block any strange connections. But watch out, RIAA is after CNET for copyright infringement because they were DISTRIBUTING Limewire, which was deemed illegal thanks to some judge. What a shock eh? So who wants to bet they’ll go after the browsers as major infringers because they don’t protect against filesharing, especially with the new API’s? you can find more on - http://www.p2pnet.net/story/50962