Ahh! Yes, that is exactly what was happening. I am using a http client library but accidentally bypassed the "dechunker" code and started reading from its raw stream without realizing I was doing so. Thanks very much!
On Nov 30, 11:28 am, "@epc" <epcoste...@gmail.com> wrote: > On Nov 29, 12:07 pm, Matt Harris <thematthar...@twitter.com> wrote: > > > What I did notice is that 0x6EF = 1775 and 0x710 = 1808 -- in both cases the > > Hex values are 6 bytes longer than the object we are returning. > > This came up in March, > see:http://groups.google.com/group/twitter-development-talk/msg/69131a43f... > Net: it appears that the client is consuming the stream raw and not > decoding the chunked transfer encoding. > -- > -ed costello -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
