I have made a proof of concept to make an grpc-web work over a websocket where i mirrored the channel implementation of the java grpc-api. The protocol over the websocket is defined in protobuf and contains metadata for each package like the stream id.
The main advantages of this implementation is:
it is easy to implement an in proxy process
all browsers support websockets
I was wondering if you are interested in this feature, I think it could be ported to the envoy proxy. (c++ is a long time ago for me).
Working proof of concept
Dear,
I have made a proof of concept to make an grpc-web work over a websocket where i mirrored the channel implementation of the java grpc-api. The protocol over the websocket is defined in protobuf and contains metadata for each package like the stream id.
The main advantages of this implementation is:
I was wondering if you are interested in this feature, I think it could be ported to the envoy proxy. (c++ is a long time ago for me). Working proof of concept