I just went back to the top of this thread and scanned down...and I think that I'm not understanding a key detail. Douglas, you're saying that the packed records have 'meta-data', but it sounds like that data is a map to the packing. So, packed data types and offsets, something of that sort.
Would it be possible to re-engineer it so that you have key summary information stored somewhere? The ideal way to optimize something slow is to not do it at all! I didn't get a sense what or if that might be. Is there a datestamp or s version stamp, or some sort of checksum that you're using to figure out if a record needs transmitting? If so, what about injecting that into the header, another field, an object field (seems like you might have a good use for an object field to serve as a key indicator store)? If this would prevent needless unpacking and needless transmission, it's potentially a big win. The break-even is that you avoid enough unpacking+transmission to pay for the extra storage cost & checks. Actually, if it were something searchable, perhaps you could search for the records that need sync using a simple index search (or searches) and then just bang through the result. I suspect I'm off the mark here, but just in case...I'm posting. ********************************************************************** 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] **********************************************************************
