[
https://issues.apache.org/jira/browse/THRIFT-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13761940#comment-13761940
]
ted wang commented on THRIFT-1125:
----------------------------------
hi Jens Geyer, first,i'm not good at ruby and i am a java developer, but after
i have reviewed the patch, i think the module Processor's method write_result
will not work well in scene which user not use multiplexing server. i will test
it tomorrow and give you a feedback.
By the way, i had write code with 'open class' in ruby and support this feature
based on java implementation in version 0.9.1
My English is not very good, please forgive me
> 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
