To look a lot of information on the Internet there is no pure c # thrift framework two-way communication case,

Some of them are the client is written by c # language, the service side is written in c + + language or other languages, other languages don't understand,

And some are two connection to the server and the client, to achieve two-way communication, this way of communication is not friendly,

I need a only the client and the server only to establish a communication source,

Thrift framework and socket two-way unlike WCF duplex implementation,

What a great god can provide the code,

CodePudding user response:

Looking forward to the following reply,

CodePudding user response:

For the original poster spiritualism, hurry back

CodePudding user response:

Hey hey, wrong again, is wrong from the root,
Thrift is itself? Is heterogeneous protocol (no independent language, platform)

As for thrift framework is what? Is based on the heterogeneous agreement RPC encapsulation
RPC is what? -- -- -- -- -- -- -- -- -- -- -- -- -- -- is a remote procedure call (RPC) -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- - as the name suggests one way is to call a remote, remote agent performs end,

So it is A -- -- -- -- -- - B agent execution -- -- -- -- -- - B
So if other notice A is B to B -- -- -- -- -- -- -- A agent execution -- -- -- -- -- A

So he is essentially a one-way process


Two-way in fact also nothing, if you want to remove the framework of the so-called, only you have to do is the most primitive heterogeneous agreement, so that you or your TCP server, client, just with you
the agreement of thrift
This typically is netty + thrift agreement or netty + Google probuffer, so that can be two-way, also can retain independent language is independent of the platform of heterogeneous agreement