It looks like you are implicitly assuming that the OS will send you
chunks of stream data that correspond to single, complete parsable
chunks. That may have worked accidentally because that happened to be
how they arrived in time, but it is definitely unreliable (as you
found). What you should do i
If you can store the offending JSON and then run it through a JSON verifier
to see if it's malformed, that'd be great. Please post the offending JSON
and the error.
Otherwise, if there is a case where disambiguation is impossible, please
give examples of the two messages types that cannot be categ
That is because there are no results to return:
http://search.twitter.com/search?q=from%3AMMFlint
Abraham
On Thu, Nov 26, 2009 at 07:13, marcin wrote:
> Hello group, I have a problem with one single url:
> http://search.twitter.com/search.json?q=from%3AMMFlint
> I integrated that json flow in m
