avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Todd (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (AVRO-405) Netty-based Java RPC server
Date Mon, 12 Apr 2010 02:45:43 GMT

     [ https://issues.apache.org/jira/browse/AVRO-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

James Todd reassigned AVRO-405:
-------------------------------

    Assignee: James Todd

> 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-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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message