OkHttp and HTTP3 support - okhttp

I would like to know information about HTTP v3 support in okhttp.
Someone knows when or if it will support the new HTTP version?
I see it would use injestors for this, but I haven't found anything updated about that.
Thanks.

You can use a bridging interceptor like https://github.com/google/cronet-transport-for-okhttp/blob/master/README.md
There are no plans for HTTP/3 support implemented in Kotlin inside of OkHttp. See https://github.com/square/okhttp/issues/907

Related

okhttp3.OkHttpClient.setProxy cannot find symbol

I updated my okhttp to okhttp3 because of vulnerability issue, but the class OkHttpClient doesn't have setProxy now. What should I do? Should I rewrite the code with new one?
Thanks.
It seems that in okhttp3, it's using proxy() for the OkHttpClient.Builder. proxy() has the same documentation as setProxy() in older okhttp.
Here are some examples using proxy().

Grpc & Rest-client context issue

I have headed into an issue with losing the grpc context while using the reactive rest-client for downstream calls. Im unsure if it is my implementation or a bug related to grpc context. It seems to be similar to: https://github.com/quarkusio/quarkus/issues/13959, but according to comment that should be fixed.
Anyway the grpc context seems to be lost when a call is made downstream with the rest-client. I have setup a reproducer repo: https://github.com/AnteLund/grpc-context-lost-reproducer which has some tests to show the issue.
Any ideas?
It was a bug. It got fixed in Quarkus 2.8 (maybe even 2.7). The context was lost during the REST client call. Now, the context is preserved between the two calls.

Missing config features on Opendayligth Rest API

I am using the YangUI on the REST API of ODL(Oxygen Release) and I want to use the config features of opendaylight-inventory but I can only see the operational ones. Like this.
¿What can be the problem?
I have solved installing the same features on a previous ODL release. I don't know why but I can't see config features on Oxygen.

Can Swagger support Protobuf or WebSockets?

I want my Swagger output to have support for Protobuf and Websockets. (Protobuf is the most important)
Based on this issue, I don't think that swagger can support that. My goal is to allow end users to see the value of the Protobuf format since they are all asking me to use JSON instead.
I would contribute myself, but I'm unfamiliar with the swagger project at that level.
Question
Is there any way to get Swagger to support Protobuf or WebSockets?

Projects using Protobuf

I'm looking for some projects using Protobuf to use as a reference for implementing complex protocols. Netty examples are preferred but not required.
ActiveMQ uses the protobuf for the underlying KahaDB Message store
The LocalTime example that comes with Netty helped me a lot to understand how to use protobuf, try to learn from it.
Link: here

Resources