removes the pain of having to create or manage your own order pipeline or billing system. It allows you to quickly sign up customers, automatically meter their usage of AWS services, have Amazon bill them based on pricing you set, and collect payments.
Tag: webservices
Repoze
Want the maturity of Zope now with the flexibility of the WSGI future? Repoze integrates Zope technologies with WSGI and reusable Python middleware.
zope is coming out to play. very cool.
GData Write APIs
In a notable but understated move, Google announced yesterday the availability of the GData JavaScript Client Library for Calendar. While on the surface this may seem like just another wrapper for the Google Calendar API like the ones provided for PHP and Java it’s actually a lot more interesting. Why? Because it’s one of the first examples of the next generation client-side APIs: one that doesn’t just let you fetch data, it lets you write data as well.
first js api that allows writes, too. at least for gdata
Simplification by Committee
In what might seem like a contradiction, OASIS has formed 6 different technical committees to simplify SOA application development.
muppets.
CSV Subscription Lists
would it be possible to have CSV as an input format for the list of feed subscriptions in Venus? That way you could use Google Spreadsheets to collaboratively manage the list of feeds
using google spreadsheets. this is so much cooler than VBA
Google Base API vs. Astoria
I should probably start out by pointing out that the title of this post is a lie. By definition, RESTful protocols can not be truly SQL-like because they depend on Uniform Resource Identifiers (URIs aka URLs) for identifying resources. URIs on the Web are really just URLs and URLs are really just hierarchical paths to a particular resource similar to the paths on your local file system (e.g. /users/mark/bobapples, A:\Temp\car.jpeg). Fundamentally URIs identify a single resource or aset of resources. On the other hand, SQL is primarily about dealing with relational data which meansyou write queries that span multiple tables (i.e. resources). A syntax for addressing single resources (i.e. URLs/URIs) is fundamentally incompatible with a query language that operates over multiple resources. This was one ofthe primary reasons the W3C created XQuery even though we already had XPath.
someone is trying to sell a thick client model here. NEED TO MAINTAIN CLIENT REVENUES
Uniform Google API
I’ve been reading the Google Data APIs blog for a few months and have been impressed at how Google has been quietly executing on the plan of having a single uniform RESTful Web service interface to their various services. Contrast this with the API efforts on Yahoo! Developer Network or Windows Live Dev which are an inconsistent glop of incompatible RESTful protocols, SOAP APIs and XML-RPC methods all under the same roof. In the Google case, an app that can read and write data to Blogger can also do so to Google Calendar or Picasa Web Albums with minimal changes. This is not the case when using APIs provided by 2 Yahoo! services (e.g. Flickr and del.icio.us) or 2 Windows Live services (e.g. Live Search and Windows Live Spaces) which use completely different protocols, object models and authentication mechanisms even though provided by the same vendor.
RESTful Web Services
about time we killed abominations like xml-rpc and ws-*
registerContentHandler
whatwg is working on registerContentHandler, which allows web services to handle mime types. this will be really useful to handle lots of downloadable mime types and reduce the need for desktop apps
Distributed annotation system
A client-server system in which a single client integrates information from multiple servers. It allows a single machine to gather up genome annotation information from multiple distant web sites, collate the information, and display it to the user
Gregor J. Rothfuss 