Google Releases an API for Their Database

Ben Wills writes "Yahoo! announced that Google Released an API last Thursday. "The service, launched Thursday, is called Google Web APIs, for application programming interfaces. The tools let noncommercial software developers "query more than 2 billion Web documents directly from their own computer programs," according to Google's Web site. For now, the service is free." Google just keeps pushing the limits."

Comments

since this article is duplicate, I want to Ask /.

[Anonymous Coward]

...how to cope with an insecure girlfriend. Specifically, one that thinks everything I say, or do, is done to ridicule her. One who is convinced that I find her stupid, when all evidence points to the contrary.

And woe betide when I occasionally criticise her for real, as opposed to in her mind.

Thanks.

Google more open to "google bombing" now?

[cetan]

An interesting article on K5

http://www.kuro5hin.org/story/2002/4/15/72154/5065

talks about how now Google bombing is even more effective with this release.

Re:since this article is duplicate, I want to Ask

[Anonymous Coward]

I would say communication is the one single thing that makes or breaks relationships, and the two of you need to just sit down and discuss this. Get it out in the open. You need to figure out where her buttons are so you can find a way to get across what you want to say without pushing them, and she needs to figure out how to tell what you are saying and understand when you are raising an issue and when are you just talking. Of course, she probably is just relaly insecure, and not willfully misconstruing things, so there may be more you can do to assuage her ego-- doing little things from time to time to make her feel you care for her and find her an interesting, intelligent person could go a long way toward changing some of her internal assumptions (at the least, when she starts critisizing you, she may subconsiously wind up assuming that what you say about how she's not stupid and you aren't mocking her is true, instead of subconsiously assuming everything is critisism). (Of course, insecurity is usually very, very deep set and it may be impossible to remove that particular facet of the problem even after years..)

If you cannot find a way to do this, maybe you two would be better off seperate. If you can't find a way to communicate over *basic* things, once an actual PROBLEM in the relationship comes up, well, you're sure as hell not going to be able to communicate about complicated things like that, and the eventual meltdown will be far, far messier and more painful than another 3 months of bickering and sex could easily justify.

Of course, these are just suggestions based on my personal experience. Not everything works in every case..

--super ugly ultraman

Re:Google is Great

[Hydrogenoid]

Err... Since Yahoo! uses the google engine, it is not that surprising that some features are in common...

Re:Google saving bandwidth?

[jlanng]

Probably not a great deal. Remember that when you're 'scraping' from HTML, you don't have to load images, css resources etc

Look here for the xml-rpc interface

[codepunk]

Google xml-rpc interface

I personally refuse to support and or recommend anyone using SOAP web services due to the patent fiasco. I asked on the xml-rpc list if anyone knew of a xml-rpc gateway and Dave Winer immediately jumped to the challange and put up a public gateway.

Thanx Dave

Re:Heh, Google faster than Microsoft. Perfect timi

[mnot]

That's not what Web Services are about.

Although current applications (and some implementations) focus on RPC-over-HTTP-using-XML (and "section 5" encoding), most of the big WS vendors believe the real meat of WS is in literal-encoded documents in long-lived message exchanges.

This buys you a lot; instead of needing to have objects at both ends, you send messages that are described by a schema; the implementations are relatively independent. WS are more flexible, more loosely coupled, and more dynamic.

In this manner, WS is closer to message queuing solutions (e.g., MQSeries, MSMQ, Tibco, etc.) than it is to Corba.

The intermediary model in SOAP hasn't been exploited much yet, but should prove interesting.

Another interesting feature of SOAP is the extensibility that Modules bring you; this should allow a number of common behaviours (like reliable delivery) to be standardized.

Finally, SOAP isn't just over HTTP; again, many vendors believe that HTTP is too limiting and tempermental to be useful for the more interesting applications.

Re:What web services were meant to be?

[SirSlud]

yeah, and the beauty is, it 'breaks' the control that corperations are attempting to leverage on their consumer base through their partnerships.

For instance, if FedEX has an API I can hook into, I am not forced to use some partner of theirs [AB Inc, for the purposes of this example] because AB Inc has special permission or some manual corperate-driven method for providing their services integrated with FedEx. Now I can hook right into FedEx myself and not be forced to follow the 'carrot' of seamless integration based on their partnership strategies that force me into 'buyins' I dont really want to participate in.