avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bo Shi (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AVRO-405) Netty-based Java RPC server
Date Mon, 05 Apr 2010 15:50:27 GMT

    [ https://issues.apache.org/jira/browse/AVRO-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12853412#action_12853412
] 

Bo Shi commented on AVRO-405:
-----------------------------

Thanks Todd; I am going to try to post an update within the next couple of days as (1) needs
a bit of a re-org into multiple files instead of one monolithic source file and (b) the frame
decoder needs some hardening against random/invalid/malicious input (e.g. AVRO-391 and THRIFT-601).
 Hopefully the async server will be less susceptible to memory-related issues.

> 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.


Mime
View raw message