avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AVRO-271) InProcessTranceiver: connect RPCs without going through any sockets
Date Wed, 30 Dec 2009 22:03:29 GMT

    [ https://issues.apache.org/jira/browse/AVRO-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795463#action_12795463

Doug Cutting commented on AVRO-271:

> Am I right that the interface would need to be changed to support a single transceiver
being used to process multiple RPCs concurrently?

That's not the intent.  It's intended to be bound to a particular destination, and proabably
(when we get our heads around authentication) a particular user, but that user might reasonably
have multiple requests outstanding to that destination using a single transceiver.  In particular,
a client proxy object has a single transceiver.  A proxy should be thread safe, no?

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

View raw message