Hey,
I haven't been able to reproduce this using my Streaming API library. When
delimited=length is sent as a parameter we will include the number of bytes
(in decimal) for the object being sent.
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.
The hex value you are seeing isn't something we're have added. Is it
possible some debug code was added to your streaming library?
One way to test is to make a request using curl only and see if the Hex
values are showing there as well. You can do this by running:
curl https://stream.twitter.com/1/statuses/filter.json -d
"track=twitter" -u YOUR_USERNAME
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Mon, Nov 29, 2010 at 7:52 AM, ianrose <ianros...@gmail.com> wrote:
> It appears to me that when using the statuses/filter streaming API
> method, elements are not length-delimited by default, even if you
> don't specify "?delimited=length". And if you DO add "?
> delimited=length", you get double length fields. For example:
>
> if I query http://stream.twitter.com/1/statuses/filter.json, I get
> something like:
>
> 64B
> { <a status update in JSON format> }
>
> 731
> { <another status update in JSON format> }
>
> <etc>
>
> If, on the other hand, I query
> http://stream.twitter.com/1/statuses/filter.json?delimited=length,
> I get something like:
>
> 6EF
> 1769
> { <a status update in JSON format> }
>
> 710
> 1802
> { <another status update in JSON format> }
>
> So its passing me a length in hex, and then a length in decimal, and
> then the actual status update. It sure seems like 'delimited=length'
> is redundant now. But was this API change ever documented? I can't
> find any announcements about it and the dev docs still describe the
> old format.
>
> thanks!
>
> --
> 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
>
--
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
