[
https://issues.apache.org/jira/browse/AVRO-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12843710#action_12843710
]
Scott Carey commented on AVRO-405:
----------------------------------
Don't forget Apache HTTP Components:
http://hc.apache.org/
This is the evolution of the old Apache Commons HttpClient. HTTP Components
adds server side components and asynchronous I/O capability.
My experience with the old HttpClient was that it was significantly better
performing and robust than the built-in sun java http client. Under high load
with a lot of concurrent connections, there was a big (50% to 100%) difference.
> 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: Todd Lipcon
>
> 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.
