Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post May 09, 2012 06:25 AM by BU XI - MSFT
May 04, 2012 04:11 PM|LINK
I was following the code given in the below link.
I modified the code to handle multi page tiff files.
Though i got it to work, I want to do the entire operation in memory i.e., without storing it in the file system.
Is there any way to do this in memory?
Or is there any alternative way to do in memory pan and zoom.
If i can get the pan and zoom functionality in memory for a single image, i can manage the handling of the multi page tiff document.
Please provide me some leads on this.
May 07, 2012 06:23 AM|LINK
Normally, when files are uploaded, they are stored on local disk and when browser looks for a link of an image, it asks the server. And it is up to the server to find the image. If the image is already in memory, then the server may respond a memory stored
At the browser side, Normally, the image is loaded into your local memory when you see and zoom.
To meet your requirement, you may yet seek advices from the author of this work.
May 07, 2012 06:53 AM|LINK
I tried to contact him. But the site shows that he has been inactive since november 2010.
That's the reason i'm posting it here.
A little more info on the project, The image is not uploaded by the user in my project. The image is actually provided by ReportViewer as i don't want report viewer to display the report as html. Since there was no option to change the presentation layout
for report viewer, I am using it to render the image as a tiff and then this piece of code displays the image wit the pan and zoom functionality.
I have so far been successful in it. The only problem is generating the dzi which is stored on the server.
Instead of storing it in the server on the physical disk, I want to use the image in memory.
Or, Is there an option to save these files on the client side instead of server side to reduce the disk usage on the server. ?
May 09, 2012 06:25 AM|LINK
The image can be considered a static file that is served by the server. And you can cache this file, so when browser requests it, it isn't always read from the disk. See if you can configure IIS to handle this.