…ive connection turned off
…etter twitter-text-java compatibility method added: z_T4JInternalJSONImplFactory#createHashtagEntity z_T4JInternalJSONImplFactory#createUserMentionEntity z_T4JInternalJSONImplFactory#createUrlEntity
correctly conducting to reading plain content instead of through gzip stream, which in the end leads for instance to a null request token and twitter complaining about 'the request token for this page is invalid'. The problem is simply that the code was assuming content-encoding header to be 'Content-Encoding' (with capitals) while twitter currently returns content-encoding header (lower case).
1) Accumulate stats based on twitter method name, instead of full URL. 2) Give the mbean a reference to the same APIStatistics instance that is used by methodCalled() to calculate stats (instead of a local APIStatistics instance that nothing else has access to, which causes the mbean to report 0's for all stats).
Creates a Status from JSON, serializes it using a configured Kryo serializer, deserializes it, and makes sure they match. Just for good measure, it prints out the difference in size between the Kryo-serialized version and JSON (it's about a 4x-5x improvement).
This is necessary for serialization systems like Kryo to be able to populate a deserialized instance.