[
https://issues.apache.org/jira/browse/AVRO-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795636#action_12795636
]
Doug Cutting commented on AVRO-271:
-----------------------------------
> the problem is that readBuffers() and writeBuffers() shouldn't be public.
These were intended to be used by servers to read requests and write responses.
But my hope of writing a generic server that's passed a Transceiver hasn't
worked out in practice, even when servers process requests synchronously, and
it definitely wouldn't work for an async server. So removing readBuffers() and
writeBuffers() altogether might make sense, and declaring that Transceiver is
for client-side use only.
InProcessTransceiver can simply implement transceive() to directly invoke
Responder#respond().
Also, what do you think of renaming InProcessTransceiver to be LocalTransceiver?
> InProcessTranceiver: connect RPCs without going through any sockets
> -------------------------------------------------------------------
>
> Key: AVRO-271
> URL: https://issues.apache.org/jira/browse/AVRO-271
> Project: Avro
> Issue Type: New Feature
> Components: java
> Reporter: Philip Zeyliger
> Assignee: Philip Zeyliger
> Attachments: AVRO-271.patch.txt
>
>
> For testing (both Avro itself, and code that uses
> Avro servers) it's sometimes handy to connect the RPCs without
> even a socket. This implementation of a Transceiver does just that.
> (This can, for users, both avoid the overhead of using sockets, and,
> in debugging, let users see stack traces that have both client
> and server code in one thread.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
