Snapshots in time of the XML output and JSON output are helpful. But I certainly believe that there could be such discrepancies. They tend to arise when our database replication lag increases. Some client requests UncachedUserA in XML, and those inaccurate counts get "frozen in time" until a cache invalidation event occurs. Then the replication lag sorts itself out, and someone requests UncachedUserB and sees the correct values.
It's a very frustrating property of our system's architecture at the moment, but one we're working on solutions for. On Wed, Mar 11, 2009 at 10:09, Damon C <[email protected]> wrote: > > I've seen this from time-to-time before, but could never really pin it > down to specific users or timeframes. > > In any case, I frequently see inconsistencies between the data in XML > and JSON representations. The example I came across last night was > with the ActiveRainMaker account. The caches have since caught up (un) > fortunately, and I don't have another example. > > In this case, though, the XML had a friends_count of ~1800 while the > JSON had a friends_count of ~800. I'm not really sure what else I can > provide and I probably didn't post before b/c it just sounds like > complaining. ;) > > Thanks! > > dpc > > -- > Damon P. Cortesi > Security Guy, Twitter Apps > www. tweetstats | tweepsearch | tweetsum .com > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
