[
https://issues.apache.org/jira/browse/AVRO-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon reassigned AVRO-405:
--------------------------------
Assignee: (was: Todd Lipcon)
Assigning to unassigned since I can't seem to assign to either of you two :)
Regrading the streaming protocol, I don't think anyone is currently actively
working on it -- other things have eclipsed it on the great priority queue :).
If either of you wanted to submit a proposal that would be great!
> 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
> Attachments: AVRO-405-for-review.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.
