Hi Kirk, In this case, it’s specific fields from one database + some pictures. The databases are not the same and its not a sync. When a record gets updated, the new data is moved (pushed or pulled) to the other server. I expect it to happen on a daily basis. The data is fairly small although some of the pictures can be a couple of MB.
I’m not a fan of ODBC and one of the computers is a Mac. I’m ok with the watched folder idea but I thought there might be something else people were using. I had thought about using SQL LOGIN but I’m not sure how it handles picture data and it looks like it does not work reliably across versions. > On Sep 8, 2016, at 7:32 AM, Kirk Brooks <lists.k...@gmail.com> wrote: > > Guy, > Interesting scenario. A couple of thoughts come to mind. > What kind of data? Are these two instances of the same database that need > to sync somehow? If so how fast does it need to happen? Is this a > 'discussion' with each db sending and receiving or more of 'fyi'? And how > much data are you looking at? > > I have zero experience with ODBC so no idea if that would be good. I > suppose you could agree on some obscure ports and use send/receive packet. > Or use http calls between the two. This would give you a real-time > connection. If you don't need that I'd go with setting up the 'watched > folder' idea and some sort of disk file. > > On Wed, Sep 7, 2016 at 11:29 PM, Guy Algot <g...@macjedi.ca> wrote: > >> Given v15s current tickle trunk of features, what would be a good way to >> send data between servers across the WAN? >> >> In the past, I’ve done it by bundling up the data in a BLOB and dropping >> it on a secure FTP site. Any better, faster, stronger methods one prefers? >> Thanks. >> ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
