Services can inherit from one another. Would it make sense for you to have one meta-service inherit from all the separate services, and just serve the meta-service?
No, this would result in a service containing hundreds, and even thousands for large applications, of functions.
By the way, multiple invocations can happen in the same connection. You don't need to create a new connection every time, though there is risk of fairness issues if you keep persistent connections. This is something we've solved with NonblockingServer in Ruby, and will be solving similarly in Java soon.
I see how you can do multiple invocations now, I skimmed over the code too quickly before.
I read THRIFT-5 and understand the fairness issue, but I see this as an implementation detail of the transport I am proposing.
-- Kind regards, Johan Stuyts
