Re: [twitter-dev] Additional Delimiter

2010-03-14 Thread John Kalucki
You appear to be looking at the raw HTTP chunk transfer encoded stream. The documentation assumes that you are using a HTTP client, not the raw TCP stream. If you are using the raw TCP stream, you can try to play games and use the chunk encoding, but there are no guarantees that the chunks will alw

Re: [twitter-dev] Additional Delimiter

2010-03-14 Thread Ed Costello
On Sun, Mar 14, 2010 at 5:43 PM, thruflo wrote: > [..] I've noticed that I'm getting an extra, undocumented, line > before each length delimiter. > What's the command you're sending to twitter and the URL you’re using? I can’t replicate this (am just getting the decimal length in the responses)

Re: [twitter-dev] Additional Delimiter

2010-03-14 Thread Ed Costello
On Mar 14, 2010, at 5:43 PM, thruflo wrote: […] > However, if you look at the third status data from above, you see that > the extra line can sometimes be a digit, in that case ``592``. Which > fairly effectively borkes the consumer. From that list you posted: 0x5DE is 1496 + 6 bytes (4 bytes for