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! :)
When you call readAll()
Okio prefers net throughput over latency, and so your messages are buffered into chunks. Instead, write a loop that repeatedly reads into a Buffer
. That'll get you messages as they arrive.
Buffer buffer = new Buffer();
while (!source.exhausted()) {
long count = response.body().source().read(buffer, 8192);
// handle data in buffer.
}
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With