in reply to letting a browser client select a file to download by inode

Others already expressed their perplexities with this idea. Personally, I've never had to do anything like this - but I've been considering the problem of "serving" (in a loose sense) files without "exposing" them. Now, an option that occurred to me is to create a temporary symlink to the actual file with File::Temp, having a separate process removing it asynchronously after a suitable timeout. I'd like to hear more experienced programmers' opinion about this scheme...

  • Comment on Re: letting a browser client select a file to download by inode

Replies are listed 'Best First'.
Re^2: letting a browser client select a file to download by inode
by leocharre (Priest) on Dec 27, 2005 at 16:29 UTC

    blazar, i want to point out that this method only tells the server what file you want- that's all!

    Your mention of a symlink is very interesting, it's a thought i had chewed on and i solved in another way thanks to the help of this posting: at job help

    What i had thought of.. was to create a temporary sym link to a file, an at job would delete the sym link in x time..

    I was very lucky to get some incredibly useful thoughts on that link up there.. and ended up streaming the thing .. much better. (the original doc resides outside of http accessible realm).

    Take a look at the streamer code</a