index > Windows Live Search: Development > Limiting results to one domain or a set of explicitly defined dom...

Limiting results to one domain or a set of explicitly defined dom...

I would like to limit the web search results to the particular Web site domain that the api is implemented on. So that all the results return will belong to this domain.

I can manually filter the results by the result Url property but because of the limit on the number of results being returned I will have to make consecutive requests to the search server until I have completely checked all results or until a tempory collection of results reaches a length equal to the total results per page limit.

In addition to the above mentioned issue. There is this request per day limit of 10,000 requests. if every search request cannot return more than 50 results per page (on average) a 50,000 item result set will take up 5000 requests of the 10,000 limit. When in fact the only results in the set I wanted may have amounted to a total of 200 results.

Any Suggestions




ddn
dangerousDotNet
use "site:domain.com"?


http://www.peterRitchie.com/Blog | MSDN Forums Moderator | Microsoft MVP - Visual Developer, C#
Peter Ritchie
dangerousDotNet wrote:

In addition to the above mentioned issue. There is this request per day limit of 10,000 requests. if every search request cannot return more than 50 results per page (on average) a 50,000 item result set will take up 5000 requests of the 10,000 limit. When in fact the only results in the set I wanted may have amounted to a total of 200 results.



The API will only allow you to see the first 250 results. You are presented 50 results at a time and can stop querying for results at any time. You will never use more than 250 / 50 = 5 queries per search term to retrieve all the accessible results.

Regards,
Frank
fmccown
reply 3

You can use google to search for other answers

 

More Articles

• not well-formed (invalid token) error
• Search News?
• Using MSN Search from aspx page - Questions on getting started
• Many weeks no problems, now java.lang.ClassCastException
• Problems with Web Service and PHP
• "Client Error"
• live.com too slow
• MSDN Article
• application ids
• Comparison of Google, Yahoo, MSN APIs
Bookmark and Share
Welcome to Bokebb   New Update  
 

New Articles

• not well-formed (invalid token) error
• AppID suddenly not working?
• MSN SEARCH SUCKS!
• optional parameters for xml
• Displaying the search result
• Use msn api search with php
• msn
• How can I turn on Child Search with MSN
• Developer Provisioning System not found
• spelling with CultureInfo = "de-De&
• Commerical Applications
• escaped XML string ---> XML?
• Unattended Soap Installation
• Search News?
• Getting more than 250 results

Hot Articles

• Many weeks no problems, now java.lang.Cl
• Developer Provisioning System not found
• MSDN Article
• A few short questions
• Unattended Soap Installation
• Use asynchronous Search API
• XmlDataSource?
• Image search?
• Alternate Sources (specifically spelling)
• message
• App Id
• msn
• Search News?
• Not able to match the results
• proxy authentication required error

Recommend Articles

• Access RunTime installations
• XmlDataSource?
• Offset and Count attributes of a SourceR
• MSN SEARCH SUCKS!
• Accessing MSN Search Web Service from Perl
• Search News?
• Yahoo API
• read am WSDL
• not well-formed (invalid token) error
• Comparison of Google, Yahoo, MSN APIs
• Getting more than 250 results
• Visual Studio Only?
• Windows Live: IE7 Search Bar
• Keywords
• Soap Exception Reference.cs Line 38