thrift-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From =?gb2312?B?wfXqu5VG?= <>
Subject Why do thrift rpc stack supports only one service per one port?
Date Wed, 16 Nov 2011 23:38:00 GMT
Hi all,

We already have a home-brew Java RPC framework. Recently we need solution for Java <-->
C++ call, so I took a few days look in thrift.
With full RPC-call stack support, thrift looked great!Thanks to the thrift team!

But I have one question, as title described, *WHY thrift be designed as one service per one
Could anybody from the thrift dev team share your design level thoughts on this question?
Further, if I wanna extend this to support multiple service per one port, do you have any
suggestion? I eager for a graceful one~

Millions of thanks ahead,
- Haomin Liu
Alibaba Inc.


This email (including any attachments) is confidential and may be legally privileged. If you
received this email in error, please delete it immediately and do not copy it or use it for
any purpose or disclose its contents to any other person. Thank you.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message