You may still want to consider this as I'm not sure to see what is the added
value i.e. if you do this the "normal" way :
- the user will choose if the file should be saved (and at which location)
or opened (it is then written in a local temp directory before being opened)
With the other solution, the only added value I see is that :
- the user will not be prompted (which is also a risk)
- it will be saved at a program defined location
For this you'll need to have the user to download/accept a java applet,
activex control, .NET control (and you need to have the Java Virutal
machine, the .NET framework or whatever technology you relly on to be
installed client side plus to deploy a security policy or have the user to
allows those operations).
They are hosted in a page using the applet or object tag. For example
http://aspnet.4guysfromrolla.com/articles/052604-1.aspx.
For now I'm really not sure it"'s worth the trouble and I would just keep
the usual behavior. Are you familiar with this ? Have you already tried an
anchor link ?
You may want also to explain a bit what you are trying to do. Sometimes
having the whole picture raises better suggestions (for example if you want
to perform many local tasks you could perhaps then have just a local
application that talks with web services or some other solution etc)...