okio
okio copied to clipboard
A modern I/O library for Android, Java, and Kotlin Multiplatform.
We saw an unactionable error from the [Options to common PR](https://github.com/square/okio/pull/586): ``` Comparing binary compatibility of against ***! MODIFIED CLASS: PUBLIC FINAL okio.Options (not serializable) ***! CLASS FILE FORMAT VERSION:...
Example run: https://travis-ci.org/square/okio/builds/526916855 Those tests are time-based which probably causes them to fail on a slow machine. Need to verify their correctness and potentially use a `FakeClock` instead of real...
This would be handy in ~4 places in OkHttp, possibly more elsewhere. ``` inline fun buildByteString(block: Buffer.() -> Unit): ByteString { val buffer = Buffer() buffer.block() return buffer.readByteString() } ```
```kt class Base64Decoder(private val reader: Reader): Source class Base64Encoder(private val writer: Writer): Sink ``` Has this feature been considered before? I'd happily put some time in to work on it....
JSON and HTTP/1 encoding has a lot of binary to string conversions. We should take inspiration from this: https://johnnylee-sde.github.io/Summary-of-fast-conversion-algorithms/
There should be a break before ‘(native)’:  https://square.github.io/okio/2.x/okio/okio/-byte-string/to-byte-string/
I have a format represented in-memory as a `ByteString` and I want to expose parts of that elsewhere in the codebase without causing needless copies.
I faced this issue writing code using `web3j` library which in turn uses `okhttp` and `okio`. After application finished few daemon threads keep running. One of them is "Okio Watchdog"....
Some operations are implemented by creating a conventional ByteString. We should cache this to limit the cost of using a SegmentedByteString.
Hello, After reading the documentation available, I would expect this simple example to potentially time out: Source source = Okio.source(new FileInputStream(file)); source.timeout().timeout(10, TimeUnits.SECONDS); source.readByte(); In this case, file is a...