Dmitriy V. Ryaboy commented on GIRAPH-37:

Avery, I don't think Finagle's issue 40 is really relevant -- it's just a 
question about whether it's possible to have a finagle-based project without 
building off Twitter's scala project scaffolding called sbt-project (and the 
answer is yes, it's pretty simple).

I'll point Marius at this Jira, perhaps he'll address some of Jacob's concerns.

As far as publishing the compiled code -- that's actually pretty handy (not 
having to regenerate the stuff all the time). Maybe we could publish a 
"giraph-rpc" artifact and make main giraph rely on that? Then most developers 
(ones who don't care about RPC) won't be exposed to this at all, *and* they'll 
save compilation time by just having maven grab the pre-generated jar.
> Implement Netty-backed rpc solution
> -----------------------------------
>                 Key: GIRAPH-37
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-37
>             Project: Giraph
>          Issue Type: New Feature
>            Reporter: Jakob Homan
>            Assignee: Jakob Homan
>         Attachments: GIRAPH-37-wip.patch
> GIRAPH-12 considered replacing the current Hadoop based rpc method with 
> Netty, but didn't went in another direction. I think there is still value in 
> this approach, and will also look at Finagle.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
For more information on JIRA, see: http://www.atlassian.com/software/jira


Reply via email to