[
https://issues.apache.org/jira/browse/THRIFT-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711591#action_12711591
]
T Jake Luciani commented on THRIFT-512:
---------------------------------------
A non-blocking server can only handle a framing transport so if we changed it
there, i'd be concerned that it would cause cause confusion.
But if that is preferred I'm ok with it.
The use case I have is the need to log write operations. Rather than
re-serializing objects to disk I'd like to capture them serialized off the wire.
> Implement TProtocol.setTransport()
> ----------------------------------
>
> Key: THRIFT-512
> URL: https://issues.apache.org/jira/browse/THRIFT-512
> Project: Thrift
> Issue Type: Improvement
> Components: Library (Java)
> Affects Versions: 0.1
> Reporter: T Jake Luciani
> Priority: Minor
>
> I'm working on a Rewindable or Peek transport that delegates to a base
> transport and buffers the read/write data for access later to the raw stream.
>
> I'm also using TNonblockingServer that currently requires a
> TFramedTransport.Factory()
> Rather than change TNonblockingServer to accept a TTransportFactory, it may
> be safer to allow TProtocol.setTransport(TTransport t) so I can just swap out
> the protocol in the Processor before it starts to read/write.
> I think if someone wanted to use spring they would need this call too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
