Question

I'm implementing a Server-Sent Events library using OkHttp. Server Sent Events works by keeping an open HTTP connection to the server on which 'events' can be streamed back to the client. The connection will only close on errors, or if the client explicitly disconnects. What's the best way to achieve this streaming behaviour using OkHttp? I've attempted to do something like: response.body().source().readAll(new Sink() { @Override public void write(Buffer source, long byteCount) throws IOException { Log.d(TAG, "write(): byteCount = "+byteCount); } @Override public void flush() throws IOException { Log.d(TAG, "flush()"); } @Override public Timeout timeout() { return Timeout.NONE; } @Override public void close() throws IOException { Log.d(TAG, "close()"); } }); With this approach I will eventually see the log message in write(), but it can sometimes take quite a while (minutes). That makes me think there might be some buffering going on under the hood and I don't get my data until the buffer is flushed. I've used curl to verify the server is behaving correctly. The data is being sent on time, I'm just not getting my callback when it arrives. My experience with OkHttp and Okio is very limited, so it's very possible I've messed something up, or have forgotten to set some option. Any help is greatly appreciated! :)

Answer 1

当您致电readAll()时，Okio更喜欢净吞吐量超过延迟，因此您的消息会缓冲到块中。相反，写一个重复读入Buffer的循环。这会在他们到达时给你留言。

Buffer buffer = new Buffer();
while (!source.exhausted()) {
  long count = response.body().source().read(buffer, 8192);
  // handle data in buffer.
}

Streaming okhttp response body

1 个答案: