Hi. Working on a custom Ktor feature to extend htt...

# ktor

[rsetkus]

Hi. Working on a custom Ktor feature to extend http cache-control to store on a permanent storage. Following default Ktor cache feature HttpCache implementation. Faced with some challenges and some obstacles which I cannot overcome:
1. HttpResponse and HttpRequest have few sub-classes but only DefaultHttpResponse and DefaultHttpRequest are public but they are annotated as @InternalAPI. I could use them to deserialize stored data but then it put the project at risk. However, this is not the main issue.
2. Even though, technically DefaultHttpResponse and DefaultHttpRequest are usable but they requires HttpClientCall instance.
3. HttpClientCall constructor is internal. Function with the same name HttpClientCall is internal also. So technically cannot create the object instance.
Briefly, HttpClientCall is main obstacle of implementing permanent cache storage. Does anybody have any idea how to overcome this?

[e5l]

@Vadim Briliantov