Streaming Databased Images Using HttpHandler

Question

For a long time now I have noticed something annoying when working on Web Application projects involving databased images on my local machine. By local I mean that it\'s a t

Answer 1

If you are serving images directly, do not forget to set the correct caching headers, i.e. etags and expires. If you don't you are really going to hit your database hard and use up your bandwidth.

You will need to handle the following http headers:

• ETag
• Expires
• Last-Modified
• If-Match
• If-None-Match
• If-Modified-Since
• If-Unmodified-Since
• Unless-Modified-Since

For an example http handler that does this check out: http://code.google.com/p/talifun-web/wiki/StaticFileHandler

Answer 2

By this:

Whenever I use an HttpHandler to display the images on my local, only a portion of the images render on each page load.

Do you mean that the same image appear on places where different images should appear or that some images appear and some doesn't show at all?

In your case the difference by switching isReusable to true is that new Business(); will be called once for multiple images. If isReusable is false the new Business(); will be called once per image. This means that if you have several images per page new Business(); will be called several times for this particular page.

Also I strongly suggest changing this:

if (context.Request.QueryString["ListingID"] != null)
{
    int listingID = Convert.ToInt32(context.Request.QueryString["ListingID"]);

with:

string listingIdParam = context.Request.QueryString["ListingID"];
if (listingIdParam != null)
{
    int listingID = Convert.ToInt32(listingIdParam);

This will save you null reference exceptions that usually surface only under heavy load. Also the above will prevent serving the wrong image to a request especially when isReusable is true.

I cannot determine what the problem was exactly but I can definitely say that setting the isReusable flag was just a workaround and doesn't fix your problem. Also when a problem like this is reproducible only in certain environment that means that either it's a thread problem or there is some difference in request handling (different web server - IIS6, IIS7, development server).

Maybe posting the Business class and it's constructor can shed some light. Also I suggest implementing some kind of error logging to trap exceptions in the handler and review them.

Answer 3

I finally got all images to render by changing the value of the IsReusable property to true:

    public bool IsReusable
    {
        get
        {
            return true;
        }
    }

Apparently, this keeps the handler in memory and able to handle multiple requests. When set to false, it had to create a new instance of the handler for each incoming request.