And cache the results of whatever you fetch. No need to grab that data on every page load.<br><br>- Ken RIckard<br>agentrickard<br><br><div><span class="gmail_quote">On 8/16/07, <b class="gmail_sendername">Jeff Griffiths</b>
<<a href="mailto:anisotropic@gmail.com">anisotropic@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On 8/15/07, Ron Dorman <
<a href="mailto:rwd@simplydigtech.net">rwd@simplydigtech.net</a>> wrote:<br><br>> I am thinking: strip down the current ASP pages to just grab the needed<br>> data, transparent to the end user, and feed it back into Drupal for use
<br>> and display. I just haven't figured out how to make this happen within<br>> Drupal.<br>><br>> A sample module will be very much appreciated and hopefully help others<br>> as well.<br><br>I would take a look at modules that use external APIs such as
<br>Flickr[1] for pointers. Essentially wha you're doing is stripping down<br>the ASP output to a web service ( plain text, xml or even JSON ) and<br>then implementing a server-side-proxy for that data in Drupal. Make
<br>sure you use curl instead of fopen as it is much faster.<br><br>cheers, JeffG<br><br>[1] <a href="http://drupal.org/project/flickr">http://drupal.org/project/flickr</a><br></blockquote></div><br>