[
https://issues.apache.org/jira/browse/AVRO-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12883021#action_12883021
]
Scott Carey commented on AVRO-405:
----------------------------------
There is no reason to delete it. If you have an improved version, you can
submit that one as well.
We have had much delay in committing this feature. This is largely the fault
of committers (like me) not reviewing the patches and providing feedback.
I personally think this is a great contribution effort and that we'll want a
Netty RPC implementation in 1.4.
I won't have time to review this in the next couple weeks. I can't speak to
the availability of any others to review.
> Netty-based Java RPC server
> ---------------------------
>
> Key: AVRO-405
> URL: https://issues.apache.org/jira/browse/AVRO-405
> Project: Avro
> Issue Type: New Feature
> Components: java
> Reporter: Todd Lipcon
> Assignee: James Todd
> Attachments: AVRO-405-coolwhy.patch, AVRO-405-for-review.patch,
> AVRO-405.patch, netty-avro.zip
>
>
> A nonblocking RPC server based on Netty should be more scalable than the
> current implementation.
> We should provide two mechanisms for interfacing the RPC server to the
> implementations:
> 1) "Blocking" RPC implementations run inside a worker threadpool.
> Implementators would not know that they're working in a non-blocking context.
> 2) "Event-driven" RPC implementations that receive requests and some kind of
> request context. They are responsible for eventually calling
> context.respond(response) or somesuch. This would allow more scalable
> interaction with downstream services.
> I propose we focus on (1) first.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
