Client URL compatibility with go client?

[markphelps]

We have a Twirp service implemented in Go and are trying to use this client to make requests in our Ruby codebase.

It seems that the Ruby client (I have only tried the protobuf version so far), does not add /twirp before the service name/method when constructing the URL.

As shown in your examples:
https://github.com/twitchtv/twirp-ruby/blob/1cecfd1b7f1990c650a5209de5b93cd1b4a99b37/example/hello_world_client.rb#L6

The user has to add the /twirp path parameter when setting the URL for the client.

This seems to be at odds with the Go client, which seems to construct that path as the Go server expects.

Example:
https://github.com/twitchtv/twirp/blob/ad6d075411e462f08e971d7efc18f4a770ac8b40/example/cmd/client/main.go#L27

As a user, I would expect that both clients operate in a similar manner, and that you would only have to set the address of your server when setting the URL with the client and not have to make sure that you add the /twirp segment.

[marioizquierdo]

The general path setup has been proposed in go Twirp a while ago:

• Initial path proposal: Proposed new routing format: /package/service/method twitchtv/twirp#55
• Removing /twirp prefix from routes: Remove /twirp prefix from routes twitchtv/twirp#91
• Specification update: Add draft of v6 specification twitchtv/twirp#80

The Ruby implementation was done already in protocol v6 to avoid having to do backwards compatible changes later. The only problem is that v6 is taking more than a year in Go to see the light 😅.

So, if you want your service to be v5 compatible, simply mount it with /twirp prefix. In the future that prefix will no longer be mandatory.