You may have noticed that several keywords on the EggHeadCafe website get converted to links (like XML for example) after the initial page loads. We refer to these as custom Smart Tags. Of course, we really don't use Microsoft's Smart Tag technology. We utilize JavaScript and IE behaviors to dynamically convert the keywords to links. One of the major challenges we faced with creating this process was not disturbing existing form elements and links. No small task...
Here's a quick example of how to use the XMLHttp object to perform a WhoIs query. You can then write your own functiosn to strip out the desired content in the page.
Does one ADO methodology fit all situations? I have seen many developers use a variety of different methods in regards to creating ADO connections and recordsets in an attempt to optimize performance. These range from putting ADO connection objects in Application and Session variables and reusing the open connection for all of their pages to creating one ADO connection per page. And of course, everything else in between.
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.
RSS
Home
Newsletter
Advertising
