Happening again today:
http://local.yahooapis.com/LocalSearchServ...6&results=1as an example...
<ResultSet xsi:schemaLocation="urn:yahoo:lcl
http://local.yahooapis.com/LocalSearchServ...ponse.xsd" totalResultsAvailable="0" totalResultsReturned="0" firstResultPosition="1">
<ResultSetMapUrl/>
</ResultSet>
−
<!--
ws13.ydn.ac4.yahoo.com compressed/chunked Wed Feb 2 11:50:14 PST 2011
-->
After hitting refresh a few times on browser:
<ResultSet xsi:schemaLocation="urn:yahoo:lcl
http://local.yahooapis.com/LocalSearchServ...ponse.xsd" totalResultsAvailable="735" totalResultsReturned="2" firstResultPosition="1">
−
<ResultSetMapUrl>
http://maps.yahoo.com/broadband/?q1=Palo+A...=pizza&tp=1</ResultSetMapUrl>
−
<Result id="28734629">
<Title>Patxi's Chicago Pizza</Title>
<Address>441 Emerson St</Address>
<City>Palo Alto</City>
<State>CA</State>
<Phone>(650) 473-9999</Phone>
<Latitude>37.445242</Latitude>
<Longitude>-122.163427</Longitude>
−
<Rating>
<AverageRating>4.5</AverageRating>
<TotalRatings>27</TotalRatings>
<TotalReviews>27</TotalReviews>
<LastReviewDate>1241377358</LastReviewDate>
−
<
etc...etc....
</Result>
</ResultSet>
−
<!--
ws11.ydn.ac4.yahoo.com compressed/chunked Wed Feb 2 11:51:20 PST 2011
-->
This makes using Yahoo Local Search API too risky, as an end user could search for something, get "0 Results" and move on, when in fact, there could be hundreds of matches for their query.