> The app is in V13 now and will be moving to V15 over the Summer so there's no 4D Object available yet.
Gotcha. I've got my main code base in V13 still and like it fine. I still feel behind on this thread...what turned out to be the source of the slowdown? Packing? Unpacking? Transmission? Some combination or interaction of the above? I ask because there are alternatives at every step. In arm-wavingly broad strokes: * Reducing the amount you need to transmit: Pays for itself quickly (usually.) * Reducing the amount you need to compare: Pays for itself quickly (or is likely to.) * Reducing the _number_ of transmissions: Can also be a big deal. On the last point, a non-4D example. Try downloading a couple of hundred individual files over FTP. Ugh. Takes forever. Now try transmitting those as a single archive. Fast. Any chance you could bundle what your remote users need in a file *in advance* (or on demand, I guess) and then transmit it as a download via a single call? You've got HTTP Get, as an example. Then they can unpack it and process it locally, even if their connection is closed. Again, not sure I'm clear on the story so I may be saying things that are kind of irrelevant. Still, from what you say, this is one of those situations where some big gains are totally possible. Those are getting harder to find these days ;-) P.S. For loops are faster, as we all know ;-) ********************************************************************** 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:[email protected] **********************************************************************
