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

ted wang commented on THRIFT-1125:
----------------------------------

i have tested it and found 
Error: test_multiprotocol(ClientTest)
  ArgumentError: wrong number of arguments (1 for 2..3)
/home/ted/ruby/thrift-client/lib/thrift_client/multiplexed_client.rb:5:in 
`initialize'
multiplexed_protocol_test.rb:19:in `new'
multiplexed_protocol_test.rb:19:in `setup'

my code is
    transport = Thrift::Socket.new('127.0.0.1', 9999)
    transport = Thrift::FramedTransport.new(transport)
    protocol = Thrift::BinaryProtocol.new(transport)
    @client = Foo::FoobarService::Client.new(protocol)

it means that this code is not compatible with old api
                
> Multiplexing support for the Ruby Library
> -----------------------------------------
>
>                 Key: THRIFT-1125
>                 URL: https://issues.apache.org/jira/browse/THRIFT-1125
>             Project: Thrift
>          Issue Type: Sub-task
>          Components: Ruby - Library
>    Affects Versions: 0.6
>            Reporter: Alex
>            Priority: Minor
>              Labels: multiplexing
>         Attachments: multiplexing_support.diff
>
>
> Attached are two files which implement multiplexing support in the Ruby 
> library. I do not consider these implementations complete, however they work 
> well for my purposes.
> On the server side:
> mp = Thrift::MultiplexedProcessor.new
> mp.register 'SomeService',  some_service_processor
> mp.register 'SomeOtherService', some_other_service_processor
> ...
> server = Thrift::SimpleServer.new(mp, transport)
> On the client side:
> some_service = SomeServiceService::Client.new('SomeService', 
> some_service_protocol)
> some_other_service = SomeOtherServiceService::Client.new('SomeOtherService', 
> some_other_service_protocol)
> You only need one transport in both cases.

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