Jeff Wendling

I'm going to close this out. If you did make it work with flatbuffers in a way that can be shared, I'd love to see it!

That is indeed interesting. I'll see if I can reproduce it locally with the details you have provided.

I reproduced it locally. I think the problem is that gogo protobuf has an older descriptor.proto. Specifically, compare this line the current upstream has: https://github.com/protocolbuffers/protobuf/blob/2a2a9b6e64e0cda49b0e5377cad58c790087e1c9/src/google/protobuf/descriptor.proto#L44 to this line in gogo:...

Sorry, I don't know why that's not working for you. I confirmed locally that it worked for me. Protoc invocations are very arcane, so I'd try double checking everything.

This should be possible. One would just need to write something that maps an incoming websocket to a [stream](https://pkg.go.dev/storj.io/drpc#Stream), and then pass that into a [handler](https://pkg.go.dev/storj.io/drpc#Handler). Do you have a...

I made demo implementations using `gorilla/websocket` and `gobwas/ws` and put them in this gist: https://gist.github.com/zeebo/ae635824205088a51031c09cb07ea553 The `gobwas/ws` code is both a client and a server, and the `gorilla/websocket` code is...

https://pkg.go.dev/go.bryk.io/pkg/net/drpc/ws is an external websocket based transport to look at as well.

Yeah, that's totally fine. I prefer typescript as well, but most importantly since you're writing it you get to choose those sorts of things.

So I tried to make https://pkg.go.dev/storj.io/drpc/drpchttp somewhat follow what I thought Twirp does, but I haven't done any testing to make sure. That may already work if you don't need...

~I pushed it up as the [exp/twirp-compat](https://github.com/storj/drpc/tree/exp/twirp-compat) branch so you can experiment with it until it's been reviewed and merged onto main. Using `go get storj.io/drpc@exp/twirp-compat` should be all that's...