How to take screenshot (thumbnail) of a web site with ASP.NET 2.0?

This article describes how to take screenshots and thumbnails of web sites with asp.net 2.0.
Article
    Title: How to take screenshot (thumbnail) of a web site with ASP.NET 2.0?
    Link: http://www.codeproject.com/useritems/website_screenshot.asp
    Author: ~Daron Yöndem

Power Outage due to Storm in North West region

A heavy Storm on Thursday night (Dec 14, 2006) blew winds at 100 mile per hour and wrecked the places around northwest.
By Sunday, Already 8 people have died due to the storm around Seattle area.
Thousands of people are of electricity for 4 - 5 days and some of them will still be out of it.

read more | digg story

Getting Rid of the Back Button Problem

For certain data sensitive web pages, you probably do not want users to use a web browser's back button because they may retrieve and repost a page from the browser's cache, which may cause an unexpected problem and sometimes crash your application. This is the so-called back button problem. Learn how to get rid of the little bug in an ASP .NET way.

---

News Feed Source
Home Page: http://www.codeguru.com/
Feed Title: CodeGuru.com
Feed URL: http://www.codeguru.com/icom_includes/feeds/codeguru/rss-csharp.xml

Article
Title: Getting Rid of the Back Button Problem
Link: http://redir.internet.com/rss/click/www.codeguru.com/csharp/.net/net_debugging/debugging/article.php/c12891
Author: ~
Publication Date:

In the "old-style" event registration model, you would typically register events by assigning functions to the onevent property of DOM elements:

elem.onclick = function() {alert("You clicked me");}

The problem with that approach is that you can only assign a single event handler function to any given event. All modern browsers support more advanced event registration mechanisms so you can attach multiple event listeners to any given event, though, as usual, those mechanisms vary across platforms. This recipe can be used to register and unregister event listeners in all modern browsers:

function addEventListener(instance, eventName, listener) {

    var listenerFn = listener;

    if (instance.addEventListener) {

        instance.addEventListener(eventName, listenerFn, false);

    } else if (instance.attachEvent) {

        listenerFn = function() {

            listener(window.event);

        }

        instance.attachEvent("on" + eventName, listenerFn);

    } else {

        throw new Error("Event registration not supported");

    }

    return {

        instance: instance,

        name: eventName,

        listener: listenerFn

    };

}

function removeEventListener(event) {

    var instance = event.instance;

    if (instance.removeEventListener) {

        instance.removeEventListener(event.name, event.listener, false);

    } else if (instance.detachEvent) {

        instance.detachEvent("on" + event.name, event.listener);

    }

}

The usage model for the functions above looks like this:

var elem = document.getElementById("elem");

var listener = addEventListener(elem, "click", function() {

    alert("You clicked me!");

});

removeEventListener(listener);

While those recipes function correctly in all major browsers, Internet Explorer has a lot of memory leak bugs that are exacerbated by event registration. While the details are a bit complex (subtle interactions between function closures and COM), we can augment the recipe above with a global event deregistration function that will remove memory leaks in most applications:

var __eventListeners = [];

function addEventListener(instance, eventName, listener) {

    var listenerFn = listener;

    if (instance.addEventListener) {

        instance.addEventListener(eventName, listenerFn, false);

    } else if (instance.attachEvent) {

        listenerFn = function() {

            listener(window.event);

        }

        instance.attachEvent("on" + eventName, listenerFn);

    } else {

        throw new Error("Event registration not supported");

    }

    var event = {

        instance: instance,

        name: eventName,

        listener: listenerFn

    };

    __eventListeners.push(event);

    return event;

}

function removeEventListener(event) {

    var instance = event.instance;

    if (instance.removeEventListener) {

        instance.removeEventListener(event.name, event.listener, false);

    } else if (instance.detachEvent) {

        instance.detachEvent("on" + event.name, event.listener);

    }

    for (var i = 0; i < __eventListeners.length; i++) {

        if (__eventListeners[i] == event) {

            __eventListeners.splice(i, 1);

            break;

        }

    }

}

function unregisterAllEvents() {

    while (__eventListeners.length > 0) {

        removeEventListener(__eventListeners[0]);

    }

}

The unregisterAllEvents function unregisters all events globally, which kills the references between the DOM objects and the listener functions, which generally prevents event registration memory leaks. To take advantage of the function, call it in the onunload handler for your page:

See a complete example

News Feed Source
Home Page:
Feed Title: Ajax Cookbook
Feed URL: http://ajaxcookbook.org/feed/

Article
Title: Cross-Browser Event Handling and Memory Leaks
Link: http://ajaxcookbook.org/event-handling-memory-leaks/
Author: ~Bret Taylor
Publication Date: 12/10/2006 9:55:27 PM