> On May 8, 2018, at 4:48 PM, David Loeppky via 4D_Tech <[email protected]> > wrote: > > I have a standalone 4D application that needs to occasionally connect to > our 4D Server to exchange some data. Realizing there are a few different > architecture approaches to take, I'd appreciate some advice as to the > easiest way to approach this.
I would second Kirk’s recommendation and I tried SQL, although not the 4D builtin replication feature, we wrote synchronization module. We rewrote the whole thing as API using HTTPs and C_OBJECT because of the speed and because we will need it for the planned native iPnone and Andorid app. Milan ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
