Bug #64471 for AnyEvent-Twitter-Stream: JSON parsing errors

Unfortunately the AnyEvent::HTTP POD still claims (on_body) .. 'is usually preferred over doing your own body handling via "want_body_handle", but in case of streaming APIs, where HTTP is only used to create a connection, "want_body_handle" is the better alternative, as it allows you to install your own event handler, reducing resource usage.' and (want_body _handle) '.. is useful with some push-type services, where, after the initial headers, an interactive protocol is used (typical example would be the push-style twitter API which starts a JSON/XML stream)'.

Also, in the code of AnyEvent::Twitter::Stream is this: "want_body_handle => 1, # for some reason on_body => sub {} doesn't work :/", though patching the module to use on_body does seem to work for me, something like this:

            want_body_handle => 0,
            on_body => sub {
                my ($content, $headers) = @_;
                $set_timeout->();
                do {
                    $on_keepalive->();
                    return;
                } unless $content;
                $self->{_json} ||= JSON->new;
                for my $tweet ($self->{_json}->incr_parse($content)) {
                    if ($on_delete && $tweet->{delete} && $tweet->{delete}->{status}) {
                        $on_delete->($tweet->{delete}->{status}->{id}, $tweet->{delete}->{status}->{user_id});
                   }elsif($on_friends && $tweet->{friends}) {
                        $on_friends->($tweet->{friends});
                   }elsif($on_event && $tweet->{event}) {
                        $on_event->($tweet);
                   }else{
                        $on_tweet->($tweet);
                   }
                }
                1;
       },

cleanup and error handling omitted.