Improving HttpHandler parallelism

[Alan Samet]

I have a performance issue related to HttpHandlers.

I've written a photo gallery application that uses HttpHandlers to
manage a virtual URL to my thumbnails. When I render the document with
the actual thumbnail URLs, the images appear to load instantly. When
using the HttpHandler, it looks as if the images are loaded one at a
time -- as if the HttpHandler execution is serialized. I assume this
is caused by ASP.NET processing the request vs. the standard IIS
static file handlers. Is there a way to improve the simultaneous image
loads?

The code in the httphandler is almost literally this (where filepath
is created via concatenation):
image = Image.FromFile(filePath);
HttpContext.Current.Response.ContentType = "image/jpeg";
image.Save(HttpContext.Current.Response.OutputStre am,
ImageFormat.Jpeg);

[bruce barker]

if you use sessions, then requests are serialized for the same user.
turn off session support. you should add code to handle head requests so
the browser can use cached images. also add timestamp info to headers
note: the browser will only do 2 requests at a time.
-- bruce (sqlwork.com)

Alan Samet wrote:

I have a performance issue related to HttpHandlers.

I've written a photo gallery application that uses HttpHandlers to
manage a virtual URL to my thumbnails. When I render the document with
the actual thumbnail URLs, the images appear to load instantly. When
using the HttpHandler, it looks as if the images are loaded one at a
time -- as if the HttpHandler execution is serialized. I assume this
is caused by ASP.NET processing the request vs. the standard IIS
static file handlers. Is there a way to improve the simultaneous image
loads?

The code in the httphandler is almost literally this (where filepath
is created via concatenation):
image = Image.FromFile(filePath);
HttpContext.Current.Response.ContentType = "image/jpeg";
image.Save(HttpContext.Current.Response.OutputStre am,
ImageFormat.Jpeg);

[Alan Samet]

That nailed it. Thanks a million.

On Feb 26, 11:56 am, bruce barker <[e-mail]:

if you use sessions, then requests are serialized for the same user.
turn off session support. you should add code to handle head requests so
the browser can use cached images. also add timestamp info to headers

note: the browser will only do 2 requests at a time.

-- bruce (sqlwork.com)

Alan Samet wrote:

I have a performance issue related to HttpHandlers.

I've written a photo gallery application that uses HttpHandlers to
manage a virtual URL to my thumbnails. When I render the document with
the actual thumbnail URLs, the images appear to load instantly. When
using the HttpHandler, it looks as if the images are loaded one at a
time -- as if the HttpHandler execution is serialized. I assume this
is caused by ASP.NET processing the request vs. the standard IIS
static file handlers. Is there a way to improve the simultaneous image
loads?

The code in the httphandler is almost literally this (where filepath
is created via concatenation):

image = Image.FromFile(filePath);
HttpContext.Current.Response.ContentType = "image/jpeg";
image.Save(HttpContext.Current.Response.OutputStre am,
ImageFormat.Jpeg);- Hide quoted text -

- Show quoted text -