Today I stumbled upon this handy tool called ‘Drip’, it is an Internet Explorer leak detector, used for debugging and testing for memory leaks in Internet Explorer (for Windows)

Over the last few months, a number of people have written to me or left comments asking questions about their memory leak issues with DHTML (or AJAX or “whatever you want to call it this week”) applications. Unfortunately, there’s not much I could offer in the way of advice that most people don’t already know. Get rid of closures, unhook your event handlers, etc. This advice just isn’t all that helpful when you’ve got a giant mess of JavaScript (often inherited) and visually detecting leak scenarios can be maddeningly subtle.

UPDATE: OutOfHanwell.com took the initiative to host Drip (a memory leak detector for Internet Explorer) after it was no longer unavailable through Joel Webber’s blog.

Drip: IE Leak Detector

/. Ninwa writes “Google has launched Google Sitemaps. It seems to be a service that allows webmasters to define how often their sites’ content is going to change, to give Google a better idea of what to index. It uses some basic XML as the method of submitting a sitemap. More information on the protocol is available in an FAQ. What’s most interesting is that Google is licensing the idea under the Attribution/Share Alike Creative Commons license. According to the Google Blog, this is being done ‘…so that other search engines can do a better job as well. Eventually we hope this will be supported natively in webservers (e.g. Apache, Lotus Notes, IIS).’ They even offer an open source client in Python.”

* bytefarmers.com sitemap.xml

* Slashdot | Google Launches Google Sitemaps