Joel Liu's Library tagged → View Popular
Chromium Blog: 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. 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. A simple example is included below.
-
You can use Google Chrome and pywebsocket to start implementing Web Socket-enabled web applications now. We're more than happy to hear your feedback not only on our implementation, but also on API and/or protocol design. The protocol has not been completely locked down and is still in discussion in IETF, so we are especially grateful for any early adopter feedback.
By Extension, Chrome Battles Firefox
-
But perhaps even more problematic for Mozilla is the extension submission process. With Chrome, for the majority of extensions, once you submit them, they are instantaneously live in the Extensions Gallery. The exceptions are if they use native code or access the file system, Google reserves the right to review them (which basically amounts to the developer signing an agreement that they have no malicious intent, and sending it to Google).
Google Opens Chrome Extensions To Developers, Will Only Review Certain Ones
-
If you are a developer working on an extension, you can simply agree to Google’s terms and upload your extension to the gallery right now. One of those terms is that Google has the right to review your extension before it’s published, but they are saying they will only do that if it includes “include an NPAPI component and all content scripts that affect “file://” URLs.” Google goes on to note that “For security reasons, developers of these types of extensions will need to provide some additional information before they can post them in the gallery.” Fair enough.
Aviary’s Chrome Extension Proves That These Add-Ons Are Going To Be Awesome
-
But the best part of Aviary’s extension is that it doesn’t slow down Chrome. While the actual Aviary editor takes up some of your CPU, the extension itself ads no bloat to the regular browsing experience. I actually have three extension installed right now and none are slowing Chrome (Chromium) at all. This gives me great hope.A few notes about Aviary’s plug-in: First, it’s not available yet only because Google has yet to launch its Extension Gallery. Supposedly, that’s coming soon for end-users but for now extension support is limited to developers being able to upload
Google Is Keeping Chrome OS Simple. Maybe Too Simple.
-
Rather than support Android apps and other sorts of apps, there is only one kind of app Google is interested in: the Web app. Chrome OS is all about making Web apps the only apps you will ever need. Which kind of makes you wonder how long we’ll need Android apps, or iPhone apps for that matter, because you know it is only a matter of time before a phone comes out running on Chrome OS.
Live From Google’s Chrome OS Event
-
This includes a full product rundown and details about the formal launch, which is expected to occur early next year.
-
We aren’t launching it today and not beta today. But we’ve made progress. As of today the code will be completely open. We’re excited to announce this.
- 23 more annotations...
Selected Tags
Related Tags
Top Contributors
Groups interested in Chrome
Highlighter, Sticky notes, Tagging, Groups and Network: integrated suite dramatically boosting research productivity. Learn more »
Join Diigo
