| Andrew Cooke | Contents | Latest | RSS | Twitter | Previous | Next

C[omp]ute

Welcome to my blog, which was once a mailing list of the same name and is still generated by mail. Please reply via the "comment" links.

Always interested in offers/projects/new ideas. Eclectic experience in fields like: numerical computing; Python web; Java enterprise; functional languages; GPGPU; SQL databases; etc. Based in Santiago, Chile; telecommute worldwide. CV; email.

Personal Projects

Lepl parser for Python.

Colorless Green.

Photography around Santiago.

SVG experiment.

Professional Portfolio

Calibration of seismometers.

Data access via web services.

Cache rewrite.

Extending OpenSSH.

C-ORM: docs, API.

Last 100 entries

OpenSuse 42.2 and Synaptics Touch-Pads; Telephone System Quotes for Cat Soft LLC; Even; Cherry Jam; Lebanese Writer Amin Maalouf; Learning From Trump; Chinese Writer Hu Fayun; C++ - it's the language of the future; And; Apricot Jam; Also; Excellent Article on USA Politics; Oh Metafilter; Prejudice Against The Rurals; Also, Zizek; Trump; Why Trump Won; Doxygen + Latex on CentOS 6; SMASH - Solve 5 Biggest Problems in Physics; Good article on racism, brexit, and social divides; Grandaddy are back!; Consciousness From Max Entropy; Democrats; Harvard Will Fix Black Poverty; Modelling Bicycle Wheels; Amusing Polling Outlier; If Labour keeps telling working class people...; Populism and Choice; Books on Defeat; Enrique Ferrari - Argentine Author; Transcript of German Scientists on Learning of Hiroshima; Calvert Journal; Owen Jones on Twitter; Possible Japanese Authors; Complex American Literature; Chutney v5; Weird Componentized Virus; Interesting Argentinian Author - Antonio Di Benedetto; Useful Thread on MetaPhysics; RAND on fighting online anarchy (2001); NSA Hacked; Very Good LRB Article on Brexit; Nussbaum on Anger; Tasting; Apple + Kiwi Jam; Hit Me; Sudoku - CSP + Chaos; Recycling Electronics In Santiago; Vector Displays in OpenGL; And Anti-Aliased; OpenGL - Render via Intermediate Texture; And Garmin Connect; Using Garmin Forerunner 230 With Linux; (Beating Dead Horse) StackOverflow; Current State of Justice in China; Axiom of Determinacy; Ewww; Fee Chaos Book; Course on Differential Geometry; Okay, but...; Sparse Matrices, Deep Learning; Sounds Bad; Applebaum Rape; Tomato Chutney v4; Have to add...; Culturally Liberal and Nothing More; Weird Finite / Infinite Result; Your diamond is a beaten up mess; Maths Books; Good Bike Route from Providencia / Las Condes to Panul; Iain Pears (Author of Complex Plots); Plum Jam; Excellent; More Recently; For a moment I forgot StackOverflow sucked; A Few Weeks On...; Chilean Book Recommendations; How To Write Shared Libraries; Jenny Erpenbeck (Author); Dijkstra, Coins, Tables; Python libraries error on OpenSuse; Deserving Trump; And Smugness; McCloskey Economics Trilogy; cmocka - Mocks for C; Concept Creep (Americans); Futhark - OpenCL Language; Moved / Gone; Fan and USB issues; Burgers in Santiago; The Origin of Icosahedral Symmetry in Viruses; autoenum on PyPI; Jars Explains; Tomato Chutney v3; REST; US Elections and Gender: 24 Point Swing; PPPoE on OpenSuse Leap 42.1; SuperMicro X10SDV-TLN4F/F with Opensuse Leap 42.1; Big Data AI Could Be Very Bad Indeed....; Cornering; Postcapitalism (Paul Mason)

© 2006-2015 Andrew Cooke (site) / post authors (content).

Google drop SOAP

From: "andrew cooke" <andrew@...>

Date: Tue, 19 Dec 2006 11:15:57 -0300 (CLST)

http://radar.oreilly.com/archives/2006/12/google_depreciates_SOAP_API.html

They're switching to the "AJAX API".
http://code.google.com/apis/ajaxsearch/documentation/

That means that the API you program against is defined in Javascript
rather than as a messaging protocol.  This is a neat approach - you
isolate the client from the implementation (in theory they could implement
the AJAX API with SOAP, but presumably they use GET/REST and return direct
HTML).  It's similar to what we do in NSA with the "client" instance of a
service.

One of the advantages of Java 1.6 is the close integration of Javascript,
so Java could call this directly.

A disadvantage of this approach is that, since it's an AJAX interface, I
assume that the return values are HTML.  If you want to process the data,
rather than present it, that means parsing the result (DOM or XSLT) - and
presumably the result is not in a fixed, well-documented format.  But from
Google's POV this is probably a feature - they're reducing the likelihood
that a middle party will subvert their branding/presentation/profits ("do
no evil" having long ago shifted to "do nothing to hurt the stock price").

Another possible problem is that persistence seems to be in the Javascript
layer.  In some ways that makes sense.  How would Google provide
server-side support persistence for third parties?  Caching can be
provided at the client (transparently, as far as the API user is
concerned), reducing server load.  However, experience with AJAX on the
Portal has shown that client-side state can be a problem when you want to
change pages.

More broadly - is this the sign that SOAP has failed?  No-one has any
faith in auto-generating code from WSDLs.  Will the VO catch on?

Andrew

Comment on this post