You can still make it "safe". The process that looks at files can look at
the file header. The file header must have a certain security code or key -
what ever you come up with. If it does not, delete the file. You can also
block ftp at the front door using proxy/firewalls so people can't even get
as far as sending a file. If it is really secure, you probably have a
firewall anyway to filter access to the port - right? Naturally, you can
always create a socket app and code the transfer and security yourself.
Remoting would also work, but not sure how much faster it would be over your
http transfer and you would still need to prog the security.
--
William Stacey, MVP
"Mario Rodriguez" <mr********@avantica.net> wrote in message
news:uG**************@TK2MSFTNGP11.phx.gbl...
FTP is an "totally unsafe" protocol and my application have strong
security requirements
"William Stacey [MVP]" <st***********@mvps.org> wrote in message
news:eA*************@TK2MSFTNGP11.phx.gbl... ftp an option for you?
--
William Stacey, MVP
"Mario Rodriguez" <mr********@avantica.net> wrote in message
news:#z**************@TK2MSFTNGP10.phx.gbl... HI people, there is an alternative way to upload files than the
ASP.NET native way? Is OK for small files but It doesn't seems to be
convenient for an application where there is a lot of paralell uploadings of huge
files (50MB-100MB)
Any idea? open source components ?
thanks