[
https://issues.apache.org/jira/browse/THRIFT-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933897#comment-14933897
]
James E. King, III commented on THRIFT-251:
-------------------------------------------
Is the original request here to allow for multiple input protocols to the same
TServer so that you could listen on both, say, TBinaryProtocol with SSL/TLS on
one port, and https on another port, etc...? Given this issue is fairly old
now (about 6 years) I'm not certain there's been any call for multiple input
protocols in a while. [~jfarrell] is this an issue we should maintain in the
backlog?
> Omniprotocol to have multi protocol over single services
> --------------------------------------------------------
>
> Key: THRIFT-251
> URL: https://issues.apache.org/jira/browse/THRIFT-251
> Project: Thrift
> Issue Type: New Feature
> Components: C++ - Library
> Reporter: Jérémie BORDIER
> Priority: Minor
>
> Inspired by the thrift like framework we have in the company i work for, i
> think it would be really cool to have an omniprotocol that would recognize
> and dispatch to real underlying protocols the current message. This would
> allow having a single service able to process request from other services in
> an efficient binary protocol, but also serve queries coming over AJAX from
> the browser via HTTP POST + JSON.
> The output protocol will be the input one to get things easier, even if
> having an output parameter in the URI (in case of HTTP request) could be
> possible in the future.
> We have all the basics to get this feature running, the JSON protocol is
> fixed (THRIFT-244) and the THttpServer transport now exists for the C++
> library (THRIFT-247)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
