Group items tagged

Note: this draft of the protocol/specification mentions annotation.

Whether 'annotation' in the Google Wave Protocol sense is comparable to annotation in the Diigo sense, I don't know.

"The Open Data Protocol (OData) is a Web protocol for querying and updating data that provides a way to unlock your data and free it from silos that exist in applications today. OData does this by applying and building upon Web technologies such as HTTP, Atom Publishing Protocol (AtomPub) and JSON to provide access to information from a variety of applications, services, and stores. The protocol emerged from experiences implementing AtomPub clients and servers in a variety of products over the past several years. OData is being used to expose and access information from a variety of sources including, but not limited to, relational databases, file systems, content management systems and traditional Web sites. OData is consistent with the way the Web works - it makes a deep commitment to URIs for resource identification and commits to an HTTP-based, uniform interface for interacting with those resources (just like the Web). This commitment to core Web principles allows OData to enable a new level of data integration and interoperability across a broad range of clients, servers, services, and tools. OData is released under the Open Specification Promise to allow anyone to freely interoperate with OData implementations."

"The Google Data Protocol is a REST-inspired technology for reading, writing, and modifying information on the web. Many services at Google provide external access to data and functionality through APIs that utilize the Google Data Protocol. The protocol currently supports two primary modes of access: AtomPub: Information is sent as a collection of Atom items, using the standard Atom syndication format to represent data and HTTP to handle communication. The Google Data Protocol extends AtomPub for processing queries, authentication, and batch requests. JSON: Information is sent as JSON objects that mirror the Atom representation."

referred from https://twitter.com/krynsky/status/5491594912

referred from http://www.diigo.com/bookmark/http%3A%2F%2Fblog.louisgray.com%2F2009%2F10%2Fproposed-salmon-protocol-aims-to-unify.html?tab=comment&uname=grahamperrin

"This document describes the Google Data Protocol used by many Google APIs, including information about what a query looks like, what results look like, and so on. "

Spartan Protocol Program Reviews

Google Wave in The Register.

According to Yahoo!'s Exceptional Performance Team, 40% to 60% of Yahoo!'s users have an empty cache experience and about 20% of all page views are done with an empty cache (see this article by Tenni Theurer on the YUIBlog for more information on browser cache usage). This fact outlines the importance of keeping web pages as lightweight as possible. Improving the engineering design of a page or a web application usually yields the biggest savings and that should always be a primary strategy. With the right design in place, there are many secondary strategies for improving performance such as minification of the code, HTTP compression, using CSS sprites, etc. In terms of code minification, the most widely used tools to minify JavaScript code are Douglas Crockford's JSMIN, the Dojo compressor and Dean Edwards' Packer. Each of these tools, however, has drawbacks. JSMIN, for example, does not yield optimal savings (due to its simple algorithm, it must leave many line feed characters in the code in order not to introduce any new bugs). The goal of JavaScript and CSS minification is always to preserve the operational qualities of the code while reducing its overall byte footprint (both in raw terms and after gzipping, as most JavaScript and CSS served from production web servers is gzipped as part of the HTTP protocol). The YUI Compressor is JavaScript minifier designed to be 100% safe and yield a higher compression ratio than most other tools. Tests on the YUI Library have shown savings of over 20% compared to JSMin (becoming 10% after HTTP compression). Starting with version 2.0, the YUI Compressor is also able to compress CSS files by using a port of Isaac Schlueter's regular-expression-based CSS minifier.

WebORB for PHP is a robust FREE and OPEN SOURCE multi-protocol development and runtime environment that is designed to effortlessly connect Flex, Flash, AJAX and Silverlight clients with PHP classes and data from relational databases via PHP backend. WebORB for PHP The goal of WebORB for PHP is to enable a new generation of web applications with enhanced UI capabilities, robust client-server communication, streamlined data synchronization, transaction services support and real-time messaging, all at a reasonable cost that delivers fast time to market.

This information is important for understanding how to coordinate access to and from cloud services.

The Internet Assigned Numbers Authority (IANA) is responsible for the global coordination of the DNS Root, IP addressing, and other Internet protocol resources.

Google Wave on the unofficial Google Operating System blog.

Your Electronics Open Source - Electronics Projects for Engineers & Hobbyists. Articles about: Embedded systems. PCB design. Power Supplies. Analog design. Firmware and device drivers development. RF and data transmission protocols and circuits.

Raindrop is an effort that starts by trying to understand today's web of conversations, and aims to design an interface that helps people get a handle on their digital world. At the same time, it creates a programming interface (API) that helps designers and developers extend our work and create new systems on top of that data. We aren't trying to invent new protocols or build new messaging systems, rather focusing on building a product that lets users get a handle on the systems we already use.

Rediffmail login Rediffmail Sign In

Hotmail login Hotmail Sign In