[jira] Commented: (THRIFT-20) encoding/decoding a ThriftStruct

["Kevin Ballard (JIRA)" <ji...@apache.org>]

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

Kevin Ballard commented on THRIFT-20:
-------------------------------------

I just committed a version of this to my own ruby stuff (pri/kballard/ruby_lib_rewrite), including specs, so when that gets accepted into svn this issue should be closed.

> encoding/decoding a ThriftStruct
> --------------------------------
>
>                 Key: THRIFT-20
>                 URL: https://issues.apache.org/jira/browse/THRIFT-20
>             Project: Thrift
>          Issue Type: New Feature
>          Components: Library (Ruby)
>            Reporter: Manish Shah
>            Priority: Minor
>         Attachments: ruby_serializer_deserializer.patch
>
>
> I'd like to define Thrift types without a service definition.  The idea being that we can define a collection of Thrift types/objects/structs that can be used by many different services and can be encoded and decoded just the same.
> Currently, a ThriftStruct gets de/encoded when being passed to (or returned from) a method in a defined service.  I could do the de/encoding with a protocol and transport myself, but it would be more convenient if there were methods to abstract this work away.
> What i'd like to do (and here is where i would like input) is to define an encode/decode method on ThriftStruct to take a type and a protocol and return back an encoded or decoded version of the type given.  The procedure would make use of the TMemoryBuffer as the transport to use by the given protocol.
> Anything wrong with this approach?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.