[
https://issues.apache.org/jira/browse/AVRO-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905300#action_12905300
]
Doug Cutting commented on AVRO-625:
-----------------------------------
Ryan, it sounds like we should make it possible to avoid connection sharing
too. A simple approach might be to continue to have a connection per client
object, as Avro does today. (Hadoop has a static cache of connections that are
shared among client objects.) Then, if a single proxy is used from many
threads, it would share the connection, but if each thread uses its own client
object it would have its own connection. Would that suffice?
Note that, with the current Avro approach, once a connection is closed then its
client instance may no longer be used: connections are not automatically
re-opened as they are in Hadoop. I don't know yet if this is a bug or a
feature.
> RPC: permit out-of-order responses
> ----------------------------------
>
> Key: AVRO-625
> URL: https://issues.apache.org/jira/browse/AVRO-625
> Project: Avro
> Issue Type: New Feature
> Components: java, spec
> Reporter: Doug Cutting
> Assignee: Doug Cutting
> Fix For: 1.5.0
>
>
> It should be possible, when using a stateful, connection-based transport, for
> a client to complete a second request over a connection before the first
> request has returned. In other words, responses should be permitted to
> arrive out-of-order.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
