Hey Tom, Thanks for scoping this out. My feeling behind the intent of OODT-123 is to not replace XML-RPC (which as a low level library still maintains lots of backwards compat dependencies e.g., on PHP and Python libraries that client connect to FM, WM and RM services). I think the intent would be to take the approach that we have taken in other places e.g., with Curator and the work that Ross Laidlaw is doing in cas-product, and to look at a REST-ful API based on JAX-RS and Apache CXF. Now there are already a set of useful features in cas-product, and curator, that expose many of the underlying FM ingestion, and curation functionalities, and data delivery.
My recommendation would be: 1. Familiarize yourself with cas-product 2. Familiarize yourself with the curator 3. Decide what services they are exposing in JAX-RS (the cas-product ones are being developed as a GSoC 2013 project by Ross Laidlaw so you may want to coordinate with him; curator ones have existed for a while) 4. Suggest some concrete updates and new services to be placed in e.g., cas-product or curator based on looking at FM XML-RPC and its API and looking at gaps there. HTH. Cheers, Chris ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -----Original Message----- From: Tom Barber <tom.bar...@meteoriteconsulting.com> Reply-To: "dev@oodt.apache.org" <dev@oodt.apache.org> Date: Tuesday, June 18, 2013 7:41 AM To: "dev@oodt.apache.org" <dev@oodt.apache.org> Subject: Help with OODT-123 >Alright guys, after chatting with Chris, I thought I'd kick off my help >with looking at OODT-123 and OODT-124. > >Now clearly I'm new to how all the components hang together but OODT-123 >seems obvious enough but I'm curious to know quite what "Port any >filemanger specific services currently in the curator over to the rest >filemanager services area" > >Now my way of working out what is what would be to look for filemgr >dependencies and acertain whether they can be removed. I assume that if >you are aiming to go rest based for communications then things like >direct connections to the XMLRepositoryManager etc would need to be >replaced with a restful representation. > >Am I on the right path or way off? > >Cheers > >Tom
