On Wed, Mar 28, 2012 at 1:46 PM, Ajay Garg <ajaygargn...@gmail.com> wrote: > Thanks a ton Waqas. > > This is probably what I was looking for. > > Just some minor queries :: > > a) > Once the proxies are setup (i.e. there is a link (Alice's WebDAV hosted in > "httpd") <==> (Tom's server) <==> (Bob's browser), then the user-experience > will be the same as though Alice and Bob are on the same network, right? > >
Yep, in the end it's just an HTTP proxy. The fact that there's a tunnel and XMPP is invisible to the WebDAV user. > b) > What is your general opinion on this approach? Would the amount and > complexity of the added code (proxy-setup) be worthwhile, than looking for a > possible alternative like > "upload-files-to-central-server-and-then-download-from-there"? > > Depends on what you are actually trying to build. Do you need realtime sync like Dropbox? Is WebDAV a requirement? Can Bob run a custom client? Is the server having a copy of the files a good thing? WebDAV isn't too great at realtime sync AFAIK. And if Bob can run a custom client, an end-to-end Jingle session between Bob and Alice would be much better than tunneling through Tom's server, since that saves bandwidth for the server, allows direct peer to peer transfers, etc. If the server would want to keep a copy of everything anyway (like it does in Dropbox's case), then "upload-files-to-central-server-and-then-download-from-there" would be better. > Anyways, thanks a ton for the confidence :) > > > Thanks and Regards, > Ajay > _______________________________________________ JDev mailing list Info: http://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: jdev-unsubscr...@jabber.org _______________________________________________
