[
https://issues.apache.org/jira/browse/THRIFT-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661012#action_12661012
]
Jérémie BORDIER commented on THRIFT-251:
----------------------------------------
Thanks for the link Michael. This is related but different yeah, but not
incompatible. Actually, this is how our framework works, services have a name
and are reachable over HTTP with /ServiceName/Method URIs... I'll get things
done step by step, but I'll keep a track about it in my fun things to do list.
> 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: Library (C++)
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
