Does Serialization have streaming parsing?

Only for JSON

Yes JSON is what I'm after. Do I need to enable something if it's plugged into retrofit/ktor?

I don't know about ktor. For Retrofit it's not supported by my converter but you could write your own fairly easily (after all, that's the whole point of Retrofits extendable design). https://github.com/JakeWharton/retrofit2-kotlinx-serialization-converter/issues/43

Right thanks! Btw, what do you mean about other textformats, like xml etc?

Yep. My converter relies on the

TextFormat

type which is in serialization core. It doesn't actually know anything about whether you're using JSON, XML, HTML, TOML, etc. The same is true for

BinaryFormat

and protobuf, CBOR, etc.

Gotcha Btw, is the assumption of staying in Square stack (okhttp+moshi+retrofit) as to use less memory because of sharing okio instances, still valid?

It helps a bit, sure. I don't think it's absolutely essential. For example, I only use kotlinx.serialization nowadays with Kotlin types. I think Moshi is great for Java, but its design for Kotlin leaves a bit to be desired. Plenty of people are still happy with it, though.

Interesting, even if you dont need multiplatform? Btw what exactly,

sealed

stuff?

BTW it is called StringFormat.

Ah yeah I think TextFormat was an early 0.x name

Yes, this is one advantage of kotlinx serialization: the format agnostic compiler plugin, so you don’t need reflection to get the scheme of the class.

There's still reflection even if codegen in moshi? That's news, thanks About retrofit though, there is not much hope for it going pure kotlin (as to be multiplatform viable) because of the java Proxy thing, right?

Maybe in the distant future it'll be a compiler plugin that generates the backing implementation rather than doing it with proxy/reflection. But as it stands, there's little reason to migrate to Kotlin.

So if you wanted to experiment with multiplatform say next year, in a existing square stack android codebase, you'd use Serialization and Ktor backed with OkHttp on android? Wondering how to translate all the Interceptors to multiplatform as its a OkHttp type. and thats supposed to be android detail

You can write a simple interface for an HTTP client and then implement it natively on each platform. That's what we do today, basically a single suspending function that takes a request and returns a response.

but what about the "middleware" stuff like auth, interceptors? rewrite those in their respective libraries as a detail? or have that be part of the http client interface?

Its HTTP model is, not the actual transport engine

which means its api?

Authenticator

and

Intereceptors

now magically become multiplatform? And I'll only need to swap the engine's engine? 😀

That's the goal. I'm not sure how far they are. Jesse and I are working on other crazy things that occupy the majority of our time so Retrofit and OkHttp haven't gotten a lot of attention

Oh, back from the parental leave already? 😀

Honestly I wasn't thinking of that but I guess kids are crazy things that occupy the majority of ones time, too

😀 nn, I though Jesse was still on the leave

I'm about to take the rest of mine in December. He took a bunch in the summer. Not sure if he's done completely or not. Plus parental leave means we get to hack on open source more since there's no real work to do.

so you don't build the serialization into the interface? So then I presume you have some sort of pure kotlin ApiClient type which combines the HttpClient (implemented per platform) and Serialization, for feature people to consume (basically retrofit reimplemented?)

We do serialization in the common code, since kotlinx is multiplatform

yes, but in essence you rebuilt retrofit, no?

It's an imperative API not a declarative one like Retrofit. Here's a very, very rough example of what I mean: https://github.com/cashapp/redwood/blob/trunk/samples/emoji-search/presenter-treehouse/src/commonMain/kotlin/com/example/redwood/emojisearch/treehouse/HostApi.kt#L24. This one is tailored to the single API call we have to make in the sample, but it's not far off of a general-purpose client either.

right, but what it does is supplants retrofit, i.e. its implementation on android is directly via okhttp, not throught retrofit again, right?

Yes

great, thanks for patience!