[
https://issues.apache.org/jira/browse/OODT-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14383961#comment-14383961
]
Radu Manole commented on OODT-808:
----------------------------------
Hello,
My name is Radu and I am a student in the 2nd year at the Alexandru Ioan Cuza
University of Iasi, Romania.
I am interested in contributing to this project. I have learned recently about
RPC and web services and I really liked to learn about the technologies used to
make this possible.
I downloaded and compiled the source code. I looked through the places where
XMLRPC is used and the number of classes seems reasonable, some of them are
really extending some abstract classes which means little will be changed
through the source code.
>From what I understand OODT uses XMLRPC for communication between the
>computers in the GRID. Is that right?
Also, what are the biggest challenges in this project?
Thank you,
Radu.
> Replace OODT's XMLPRC with Avro's RPC
> -------------------------------------
>
> Key: OODT-808
> URL: https://issues.apache.org/jira/browse/OODT-808
> Project: OODT
> Issue Type: Task
> Components: xmlps
> Reporter: Lewis John McGibbney
> Labels: gsoc2015
> Fix For: 0.9
>
>
> OODT relies on a legacy [Remote Procedure
> Call|http://en.wikipedia.org/wiki/Remote_procedure_call] implementation,
> namely [Apache XML-RPC|https://ws.apache.org/xmlrpc/]. Our version of this
> library currently sits at 2.0.1, which was released on 28th December 2005.
> This issue proposes to replace the convoluted XML-RPC logic with [Apache
> Avro's|http://avro.apache.org] [RPC
> Protocol|http://avro.apache.org/docs/1.7.7/spec.html#Protocol+Declaration]
> implementation.
> Right now xmlrpc implementation logic exists in the following OODT modules:
> * catalog
> * commons
> * crawler
> * filemgr
> * mvn
> * pcs
> * protocol/api
> * pushpull
> * resource
> * workflow
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
