15: Understanding WSDL and Web Services in .NET

Generation QR Code JIS X 0510 in .NET 15: Understanding WSDL and Web Services

"wrapper"

One of the best of these wrappers is XooMLe You can find out more information about XooMLe at wwwdentedrealitycomau/xoomle/ Using the XooMLe site, you can run HTTP queries against Google and get XML responses back Things really do start to get fun (and useful) when you use XooMLe to run queries against the Google Web APIs service using a URL and HTTP! Essentially, any query you can run using the Google APIs, you can run against XooMLe using HTTP Of course, by using an intermediary you are adding processing overhead to any query You need to have your Google developer key in hand to query Google via XooMLe using HTTP Here s how you can use XooMLe to run the doGoogleSearch Google API using HTTP: 1 Open a URL of the following format in your Web browser:

Insert the long code of letters, numbers, and other characters in place of GoogleDeveloperKey There should be no line break when you type this code string The URL is composed of your developer key and your query string 2 You can also tack on any of the other doGoogleSearch arguments after the search string if you d like; for example, to return only the first result for a given search query, type

TEAM LinG - Live, Informative, Non-cost and Genuine !

Comparable XooMLe addresses are available for the other two Google APIs If the call to the Google API is successful, your results page is returned in XML format If there are problems, a detailed error page is returned instead

One significant wrinkle to the easy process of using XooMLe is that you need to make sure that your developer key, the query string, and any other arguments contain only characters that can be transmitted through HTTP Some nonalphanumeric characters, for example a plus sign (+) in the developer key, need to be URL encoded so they can go through HTTP In a nutshell, URL encoding of a character consists of a % symbol, followed by the two-digit hexadecimal representation (case-insensitive) of the ISO-Latin character code for the letter You can learn more about this by conducting a Google search for URL encoding You may need to experiment via trial and error to find out exactly which characters need to be URL encoded, and which don t Say you want to call the XooMLe doGoogleSearch with the following developer key and search string: Developer key: wlCj3+cTSgCKTJH/amit56sKWOKtk9 Search string: braintique writing Using these values, your URL would look like this:

Opening this URL in a browser returns an error message stating that the developer key isn t valid The problem is with the + in the developer key (although for some reason the plus sign that separates search terms doesn t cause a problem) If you re running Windows, the easiest way to find the character code for a character that needs to be encoded is to use the Character Map dialog box: 1 From the Windows Start menu, choose All Programs Accessories System Tools Character Map The Character Map dialog box opens

TEAM LinG - Live, Informative, Non-cost and Genuine !

2 Locate the symbol that you suspect HTTP won t accept and click it See Figure 15-2 3 Run your mouse across the thumbnail of the symbol to see its Unicode equivalent The Unicode equivalent also appears in the lower-left corner of the dialog box In this case, the URL encoded replacement for the plus sign is %2B (the Unicode number shown is +002B, which is the same as 2B, which is %2B when URL-encoded) 4 Close the dialog box when you re done