Web developers will have the ability to leverage the 250 million users of Yahoo Mail as they create innovative and interesting applications based on the product; Yahoo Mail vice president John Kremer can’t wait to see what they do.

I’ll have more to say about some of the larger issues around this in a few days, but now that the embargo has been lifted (damn you, Om Malik), I wanted to point at the pair of announcements from Yahoo! Mail today and yesterday.

I recently went to a soap shop in downtown San Fransisco called Lush. It is the most expensive soap I have ever seen, and a perfect product for the web. My girlfiriend asked the clerk if they sold online and they said yes, but don’t buy Lush soap from Amazon.com.

Google stopped issuing keys for its SOAP Search API in early December, in favor of promoting its Ajax Search API for developers who want access to Google results. Or is it?

Mark Lucovsky, of Google, posted that Google has replaced its SOAP API with its AJAX Search API.

There are many webmasters who leverage Google’s search results and other related data by using their SOAP API. However, what are these folks to do now that Google is no longer supporting it?

Joshua Bloch has a good presentation outline called How to Design a Good API and Why it Matters.

Have you ever wanted to enrich your site with information from Google, Amazon, eBay, or one of the many other sites that provide web services through SOAP?

It’s a great place, the blogosphere. Anyone with an opinion about anything can articulate it. And anyone does precisely that, including me.

In this article, my goal is to provide you with a thorough AJAX primer and give you a real-world illustration of its usefulness.

The online retailer has added a new service for users: a low-cost virtual closet where people can put in and take out their data online, and pay for just what they store and transfer.

Google’s SafeSearch proved to be less than safe when used with Google Base, but the glitch that caused some unsavory results to appear in searches has been fixed.

As we’ve discussed in the previous installments of this article series, Web services are comprised of a number of core standards, including:

Starting in April 2002, I began a long-running article series titled, An Extensive Examination of the DataGrid.

Some commercial Web services software provides sophisticated Web services accounting features, recording details of Web services transactions recognized on the wire. But sometimes developers need accounting that is more modular, much more basic, and available on a shoestring. This article explains how to use advanced function composition tasks to add basic Web services monitoring capabilities.

Unless the message exchanges of Web services are made reliable, organizations will not be able to trust them for deployment in industrial-strength business. In this paper, Prasad Yendluri, Principal Architect at webMethods, explains why there is a need for a reliable messaging solution that is independent of the underlying transport protocol used to transmit the messages, and gives an analysis of emerging Web services reliable messaging standards and the work done in this space previously by RosettaNet, BizTalk, and ebXML that forms the basis for the advancements in the Web services domain.

The World Wide Web Consortium has released Version 1.2 of the Simple Object Access Protocol (SOAP) as a formal standard.

One of the most common categories of questions on the SOAP::Lite mailing list is how to get Perl SOAP applications to work with .NET services. It’s not that Perl and SOAP::Lite are not suited to the job, but rather that there are easy traps to fall into. Add to that the fact that .NET has its own distinct philosophy toward applications, and the confusion is understandable. This article will cover some of the most common traps and considerations that trip up Perl developers.

Just like the TV soaps, the search industry has a strange and illogical history. We started with a particular cast of search engines, new ones soon rose up and tried to usurp market share from the originals, some engines jumped into bed with each other, some of the well known characters died or were killed off by the newcomers, “good” engines decide to turn “evil” in the grab for market share, new industry darlings were born and so on.

We just recently opted to make EggHeadCafe.com’s content library available via a web service. This would allow other web sites to include our links and potentially generate more traffic to the site. So, we needed an efficient way to allow others to access our data with the least amount of strain on our servers. Naturally, the topic of using a SOAP web service came up and turned out to be the most logical choice.