[英]How do I consume Twitter Streaming API in android using okhttp3?
我想繼續使用流響應。 到目前為止,這是我的代碼。 我想我無法長時間保持連接打開。
OkHttpOAuthConsumer consumer = new OkHttpOAuthConsumer("**********",
"**********");
consumer.setTokenWithSecret("***********",
"*************");
OkHttpClient client = new OkHttpClient.Builder()
.addInterceptor(new SigningInterceptor(consumer))
.build();
Request request = new Request.Builder()
.url("https://stream.twitter.com/1.1/statuses/filter.json?track=twitter")
.build();
client.newCall(request).enqueue(new Callback() {
@Override
public void onFailure(Call call, IOException e) {
e.printStackTrace();
}
@Override
public void onResponse(Call call, final Response response) throws IOException {
final String responseData = response.body().string();
Log.d("RESPONSE TWEETS" , responseData);
}
});
我收到以下異常:
Callback failure for call to https://stream.twitter.com/...
01-22 13:03:25.238 27785-28965/in.androidlab.twittervisualiser D/OkHttp: java.net.ProtocolException: unexpected end of stream
01-22 13:03:25.239 27785-28965/in.androidlab.twittervisualiser D/OkHttp: at okhttp3.internal.http1.Http1Codec$ChunkedSource.read(Http1Codec.java:433)
01-22 13:03:25.239 27785-28965/in.androidlab.twittervisualiser D/OkHttp: at okio.RealBufferedSource.read(RealBufferedSource.java:45)
01-22 13:03:25.239 27785-28965/in.androidlab.twittervisualiser D/OkHttp: at okio.RealBufferedSource.exhausted(RealBufferedSource.java:55)
01-22 13:03:25.239 27785-28965/in.androidlab.twittervisualiser D/OkHttp: at okio.InflaterSource.refill(InflaterSource.java:101)
01-22 13:03:25.239 27785-28965/in.androidlab.twittervisualiser D/OkHttp: at okio.InflaterSource.read(InflaterSource.java:62)
01-22 13:03:25.239 27785-28965/in.androidlab.twittervisualiser D/OkHttp: at okio.GzipSource.read(GzipSource.java:80)
01-22 13:03:25.239 27785-28965/in.androidlab.twittervisualiser D/OkHttp: at okio.Buffer.writeAll(Buffer.java:996)
01-22 13:03:25.239 27785-28965/in.androidlab.twittervisualiser D/OkHttp: at okio.RealBufferedSource.readString(RealBufferedSource.java:189)
01-22 13:03:25.239 27785-28965/in.androidlab.twittervisualiser D/OkHttp: at okhttp3.ResponseBody.string(ResponseBody.java:174)
01-22 13:03:25.239 27785-28965/in.androidlab.twittervisualiser D/OkHttp: at in.androidlab.twittervisualiser.MainActivity$1.onResponse(MainActivity.java:104)
01-22 13:03:25.239 27785-28965/in.androidlab.twittervisualiser D/OkHttp: at okhttp3.RealCall$AsyncCall.execute(RealCall.java:135)
01-22 13:03:25.239 27785-28965/in.androidlab.twittervisualiser D/OkHttp: at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
01-22 13:03:25.239 27785-28965/in.androidlab.twittervisualiser D/OkHttp: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
01-22 13:03:25.239 27785-28965/in.androidlab.twittervisualiser D/OkHttp: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
01-22 13:03:25.239 27785-28965/in.androidlab.twittervisualiser D/OkHttp: at java.lang.Thread.run(Thread.java:818)
我也嘗試過使用 WebSocketListener。 我在 onMessage() 中沒有得到任何響應
WebSocketListener listener = new WebSocketListener() {
@Override
public void onOpen(WebSocket webSocket, Response response) {
super.onOpen(webSocket, response);
Log.d("RESPONSE Twitter", response.message());
}
@Override
public void onMessage(WebSocket webSocket, String text) {
super.onMessage(webSocket, text);
Log.d("RESPONSE Twitter", text);
}
@Override
public void onMessage(WebSocket webSocket, ByteString bytes) {
super.onMessage(webSocket, bytes);
}
@Override
public void onClosing(WebSocket webSocket, int code, String reason) {
super.onClosing(webSocket, code, reason);
}
@Override
public void onClosed(WebSocket webSocket, int code, String reason) {
super.onClosed(webSocket, code, reason);
}
@Override
public void onFailure(WebSocket webSocket, Throwable t, Response response) {
super.onFailure(webSocket, t, response);
}
};
WebSocket ws = client.newWebSocket(request, listener);
https://stream.twitter.com/1.1/statuses/filter.json?track=twitter不是 websocket 調用。 請參閱https://dev.twitter.com/streaming/overview
您需要將其作為流式常規 HTTP 調用進行處理。
如此處所述https://github.com/square/okhttp/wiki/Recipes
但是,如果響應主體很大(大於 1 MiB),請避免使用 string(),因為它會將整個文檔加載到內存中。 在這種情況下,更喜歡將主體作為流處理。
這是一些用於將響應作為流處理的示例代碼
@Override public void showOutput(Response response, boolean showHeaders) throws IOException {
BufferedSource source = response.body().source();
Sink outputSink = getOutputSink(response);
try {
writeToSink(source, outputSink);
} finally {
if (!isStdout()) {
outputSink.close();
}
}
}
public static void writeToSink(BufferedSource source, Sink out) throws IOException {
while (!source.exhausted()) {
out.write(source.buffer(), source.buffer().size());
out.flush();
}
聲明:本站的技術帖子網頁,遵循CC BY-SA 4.0協議,如果您需要轉載,請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.