I have been working through this as well, code can be found at: http://github.com/jwtodd/netty-avro
would love to collaborate. - james On Mon, Apr 5, 2010 at 12:03 AM, Bo Shi (JIRA) <j...@apache.org> wrote: > > [ > https://issues.apache.org/jira/browse/AVRO-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12853324#action_12853324] > > Bo Shi commented on AVRO-405: > ----------------------------- > > Anyone working on this? I had a bit of free time this weekend to go > through the avro and netty tutorials and threw together something that might > fit the bill. The implementation is mostly plumbing; I put together frame > encoding and decoding a handler that wraps a Responder instance. Would > welcome any comments. > > > 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 > > Attachments: AVRO-405-for-review.patch > > > > > > 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. > >
