You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "James E. King, III (JIRA)" <ji...@apache.org> on 2017/03/30 21:26:41 UTC
[jira] [Resolved] (THRIFT-4113) Provide a buffer transport for
reading/writing in memory byte stream
[ https://issues.apache.org/jira/browse/THRIFT-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James E. King, III resolved THRIFT-4113.
----------------------------------------
Resolution: Fixed
Assignee: James E. King, III
Fix Version/s: 0.11.0
Committed - thanks.
> Provide a buffer transport for reading/writing in memory byte stream
> --------------------------------------------------------------------
>
> Key: THRIFT-4113
> URL: https://issues.apache.org/jira/browse/THRIFT-4113
> Project: Thrift
> Issue Type: New Feature
> Components: Rust - Library
> Reporter: Chao Sun
> Assignee: James E. King, III
> Fix For: 0.11.0
>
>
> Currently the Rust support doesn't seem to have the ability to take a input byte stream and deserialize it with a particular protocol. The same for the write path. [TBufferTransport | https://github.com/apache/thrift/blob/master/lib/rs/src/transport/mem.rs#L42] seems to be the closest one but it is not exposed. Also, it copies the data to a intermediate buffer, which could be costly when deserializing large byte streams.
> We should implement something similar to CPP's [TMemoryBuffer | https://github.com/apache/thrift/blob/master/lib/rs/src/transport/mem.rs#L42] which provides 3 flavors of how the input buffer can be treated. IMO We can start by modifying TBufferTransport and make it public.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)