Allow binding more than one Thrift service at the same path

A user wants to write a Thrift proxy server that forwards the requests to their corresponding remote Thrift services where each Thrfit service has different IDLs, e.g.

service FooService {
    string foo()
}
service BarService {
    string bar()
}

If a client calls foo() then FooService would be invoked. bar() then BarService.

Currently, a user has to use TMultiplexed protocol and specify a service name explicitly.

Once this feature is implemented, a proxy Thrift server could provide a union/merged view of multiple Thrift services without using TMultiplexed protocol, allowing a user to split/merge their services without affecting the public API.

[trustin]

@sivaalli That’s a good question. I think we can add such an option later if requested by users. Meanwhile, let’s stick to the current behavior - using the same default/available serialization formats.

[trustin]

@sivaalli Thanks for looking into this issue first of all.

Is my understanding right here?

Yes, we should look for a function in the order as specified when building a THttpService.

Also, if FooService and BarService both have foo(), the FooService, which was specified first, will be chosen.

Please also keep in mind that we also need to support TMultiplexed, which is supported via of(Map) factory method. Let me know if you are not familiar with TMultiplexed - I can elaborate on it.