You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Michael Greene (JIRA)" <ji...@apache.org> on 2009/01/06 02:01:44 UTC

[jira] Commented: (THRIFT-251) Omniprotocol to have multi protocol over single services

    [ https://issues.apache.org/jira/browse/THRIFT-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661008#action_12661008 ] 

Michael Greene commented on THRIFT-251:
---------------------------------------

See https://issues.apache.org/jira/browse/THRIFT-66 for a related, but different, idea that hasn't gained much traction so far because of its broader scope.

> 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.