> The deal breaker is that the code is only updating about 3 records per > second it can sometimes takes days for the server to catch up.
Ouch, that is slow. I haven't followed closely...if your'e using SOAP, it has to escape binaries to Base64...which is an absolutely hideous wire format. If your'e trying to send a lot of binary data, base 64 is *not* your friend. It works, but it makes your payloads just stupidly large. Unless I'm wrong and you're getting the space back via compression. I think that 4D added a special option for 4D:4D SOAP communications for exactly this case. You mentioned 4D Open. One of its strengths was using 4D's (binary) wire format. If you need to send binary objects in a smarter way, there are options...but, again, I suspect I'm well off the main point here. ********************************************************************** 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 **********************************************************************
