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

Philip Zeyliger updated AVRO-271:
---------------------------------

    Attachment: AVRO-271.patch.txt

>  So removing readBuffers() and writeBuffers() altogether might make sense, 
> and declaring that Transceiver is for client-side use only.

Makes sense.  Let's do a separate JIRA for that.

> InProcessTransceiver can simply implement transceive() to directly invoke 
> Responder#respond().

Indeed; makes it even simpler.

> Also, what do you think of renaming InProcessTransceiver to be 
> LocalTransceiver?

I like it.  Done.

> 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, 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.

Reply via email to