You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Kevin Clark (JIRA)" <ji...@apache.org> on 2008/06/18 04:08:45 UTC

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

     [ https://issues.apache.org/jira/browse/THRIFT-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Clark resolved THRIFT-20.
-------------------------------

    Resolution: Fixed

Resolved by push of patches in THRIFT-38. Thanks for the contribution!

> 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
>            Assignee: Kevin Clark
>            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.