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

James E. King, III commented on THRIFT-1915:
--------------------------------------------

Good point, the solution in THRIFT-66 is compatible with the binary protocol 
because it had that spare byte in it and that's what I planned to use in my 
project at the time, but I didn't implement a solution for any other protocol, 
however conceptually they would be more obvious in text based protocols like 
JSON or HTTP, it would require changes to each protocol to support the channel 
concept.  Another worry I had which was not a problem where the project was 
being used (since it was all C#) was whether all clients initialized that part 
of the VERSION_1 header to zero or not.  It appeared that they did.
                
> Multiplexing Services
> ---------------------
>
>                 Key: THRIFT-1915
>                 URL: https://issues.apache.org/jira/browse/THRIFT-1915
>             Project: Thrift
>          Issue Type: Improvement
>          Components: AS3 - Library, Build Process, C glib - Library, C# - 
> Library, C++ - Library, Cocoa - Library, Compiler (General), D - Library, 
> Delphi - Library, Deployment, Documentation, Erlang - Library, Go - Library, 
> Haskell - Library, Java - Library, JavaME - Library, JavaScript - Library, 
> Node.js - Library, OCaml - Library, Perl - Library, PHP - Library, Python - 
> Library, Ruby - Library, Smalltalk - Library, Test Suite, Tutorial, Website
>    Affects Versions: 1.0
>            Reporter: Roger Meier
>            Priority: Blocker
>
> This is the parent Topic for the 1.0 release to introduce *Multiplex 
> Services* with Apache Thrift.
> We need sub tasks here to manage language support, test suite, documentation 
> & co.
> e.g. integrate Multiplex Services into cross language test suite THRIFT-847 
> via test/test.sh

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to