[
https://issues.apache.org/jira/browse/THRIFT-5034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paulo Neves updated THRIFT-5034:
--------------------------------
Summary: Allow for Reverse Connection servers (was: Allow for Reverse
Connection serveres)
> Allow for Reverse Connection servers
> ------------------------------------
>
> Key: THRIFT-5034
> URL: https://issues.apache.org/jira/browse/THRIFT-5034
> Project: Thrift
> Issue Type: Improvement
> Reporter: Paulo Neves
> Priority: Major
>
> Hello,
> One of the reasons I migrated from gRPC to Thrift was because of the
> fundamental distinction between RPC Client/Server and Transport
> Client/Server. This has allowed me to create RPC processors that actually
> connect to a server(broker), in a similar way to a reverse proxy. This is
> immensely useful for restricted networks.
> As said, due to the elegant separation between processor and transport this
> turned out to be trivial and I would like to share my implementation of such
> a transport "decorator" so that we can have Client transports work in
> Processor servers.
> I do not have tests yet, besides my own working private implementations but
> will try soon to prepare such for at least the Socket examples.
> I also do not know very well how the naming should be so i just made it
> TReverseTunnelServer.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
