how about creating a folder with a name 'sessionid' (on-the-fly), and copying the file. or generate a folder with any random name on the fly, temporarily, and send the client a link to it, that way it would be efficient, by not using CPU resources off your server. this whole structure would be under the apache htdocs path somewhere. and then just provide a link.
***************************************** Amit Wadhwa Technical Support Representative, Dell International Services, Bangalore ***************************************** -----Original Message----- From: Jayaprakasam, Yogaraj (Cognizant) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 11, 2002 10:31 AM To: [EMAIL PROTECTED] Subject: Re: File Reading! You are absolutely right Amit, but the problem here is the limit on the file size. We actually do not have a file size limit. Which may kill the webserver. So our approach should be as efficient as the web server handles this. Do you have any other idea for the same? Thank you very much for your input. Yogaraj -----Original Message----- From: Amit Wadhwa [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 10, 2002 12:05 PM To: [EMAIL PROTECTED] Subject: Re: File Reading! use a seperate program to read the actual file on the actual path on the server and throw it using an output stream to the client on-the-fly. that will also provide security by not letting anyone know what 'http' path do the fiels come from ***************************************** Amit Wadhwa Technical Support Representative, Dell International Services, Bangalore ***************************************** -----Original Message----- From: Jayaprakasam, Yogaraj (Cognizant) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 10, 2002 2:08 AM To: [EMAIL PROTECTED] Subject: File Reading! Hello All, My project as an requirement to publish different type of files (Word,Excel,PPT,zip etc) on the web. Our web page should have a link to those files on click of it, the corresponding files must be opened either on the web page or downloaded to the client machine and facilitate the user to read it. But our problem is either our files may eventually be residing on a separate file server or on the same machine, where our web server will be running. Here, if our files are going to be residing on a different machine, we can either make the network mapping and create on virtual directory for that folder and give the link on our browser to allow the user to open those files on the same browser or we can read the content of the file and push it to the browser. The first point is ok, if our client allows us to create a virtual directory to the file server. If that is ruled out then I need to go to the file reading. Now, my questions is, is there any such component available already out there which will be as efficient as the webserver virtual mapping and serve the same purpose? Can you guys please throw some light on this? Expecting your valuable suggestions in this regard. Regards, Yogaraj =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". Some relevant FAQs on JSP/Servlets can be found at: http://archives.java.sun.com/jsp-interest.html http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.jsp http://www.jguru.com/faq/index.jsp http://www.jspinsider.com =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". Some relevant FAQs on JSP/Servlets can be found at: http://archives.java.sun.com/jsp-interest.html http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.jsp http://www.jguru.com/faq/index.jsp http://www.jspinsider.com