jabcoco
asked on
How and why using a image handler (ashx) instead of webrelative path to display images?
Actually we only have 1 front-end server, but planning to move into a webfarm with multiple front-end server and 1 access point datastorage("SAN/SAS") to stores all the photos/videos.
Actually we simply use <img src="/images/somepath/imag e.jpg"> to display the image on client site. But we will not be able to do so eventually cause we are moving into webfarm and datastorage.
Someone told me that i need to create a "Image Handler (ashx)" who return the images.
What about the performance and memory load of using a image handler to display images. And what about "file lock" if 2 front-end server try to send back the same images?
Any example?
Thanks!!!
Actually we simply use <img src="/images/somepath/imag
Someone told me that i need to create a "Image Handler (ashx)" who return the images.
What about the performance and memory load of using a image handler to display images. And what about "file lock" if 2 front-end server try to send back the same images?
Any example?
Thanks!!!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks!
ASKER
would you also told me why i should use "ashx" intead of a normal relative server path to display images?