Decouple IO functions and dependencies into own module

[morki]

It would be awesome to have these things decoupled to minimize dependencies and to be more focused with the core library.
Like it was done with network module.

Examples:

• remove OKIO dependencies
• remove Gzip functions
• remove file access operations (OKIO)

In future there will be kotlinx-io stabilized and can be added as different module.

Is it something that you can think of?

[itboy87]

I agree with the idea of decoupling non-essential components from the ksoup library to minimize dependencies and enhance focus on the core functionalities.

Here are my thoughts on the suggestions:

Removing OKIO Dependencies:

Right now, ksoup needs okio.Buffer to work. But, we can put it in a separate module called ksoup-io. This will make the main part of ksoup better.

Removing Gzip Functions:

Yes, you're right. We can remove Gzip functions from core module. So, we can make a new module just for Gzip and give it out separately. This modular approach enables users to opt for Gzip functionality if needed.

Removing File Access Operations (OKIO):

We can move OKIO I/O code to ksoup-io too, but we won't make a separate artifact for it. ksoup still needs OKIO to work right, and these file operations are a part of OKIO.

Switch to kotlinx-io

Yes, we already have a plan to switch to using kotlinx-io.

Thanks.

[itboy87]

I'm looking at korio core https://docs.korge.org/getting-started/, and it seems like a much better option right now. It has all the required things in the library but also includes a few extra features like JSON, XML parsers, and a few others, which we can exclude. I'm testing a few things, and if it goes well, then I think we can use its streaming APIs, Charset, and CharReader, Gzip compression, which appear to be more stable. Currently, I'm using charset encoding from Ktor, which doesn't support many charsets on Node.js, but Korio has better support for it.