It took years to get sftp, http, webdav, p2p solution, blah blah blah to the states they are in. Every time I see someone talk about developing their own file transmission system I laugh.
Figure out how to incorporate something that already exists - for example have your client app use ftp to move to a folder on a server whose folder is monitored, that target folder acts as a staging location where your server-side app can then move it to wherever it really goes, so you are using established technology and putting a little bit of abstraction in so clients don't have direct access to the server's files. Your client can pass some basic metadata to your server app through a standard socket or http request or whatever, then your server app can have some knowledge of what file it should be monitoring and any 'custom' attributes you need to apply... On Fri, Aug 5, 2011 at 7:35 AM, Tim Jones <[email protected]> wrote: > On Aug 5, 2011, at 4:34 AM, MBS mailinglist wrote: > > > Hello, > > > > I need a client / server solution that would allow me to send a file > securely (encrypted) over the internet. > > Perfect would be resume of interrupted transfers. > > Heinz, > > Why not simply use scp from a shell? You can set up the shared keys > between the machines and the copy away using a known and solid protocol. > Plus, any Unix-level permissions are kept intact. > > Check out this blog: > > http://blogs.oracle.com/jkini/entry/how_to_scp_scp_and > > HTH, > Tim > > > _______________________________________________ > Mbsplugins_monkeybreadsoftware.info mailing list > [email protected] > > https://ml01.ispgateway.de/mailman/listinfo/mbsplugins_monkeybreadsoftware.info > _______________________________________________ Mbsplugins_monkeybreadsoftware.info mailing list [email protected] https://ml01.ispgateway.de/mailman/listinfo/mbsplugins_monkeybreadsoftware.info
