I couldn't have said it any better Tom.
On Wednesday, September 16, 2015, Mallder, Valerie < valerie.mall...@jhuapl.edu> wrote: > Thanks Tom! That helps a lot. I am new to this XML RPC world, so I > appreciate knowing a little bit about the 'big picture'. > > Val > > > > Valerie A. Mallder > New Horizons Deputy Mission System Engineer > Johns Hopkins University/Applied Physics Laboratory > > > > -----Original Message----- > > From: Tom Barber [mailto:tom.bar...@meteorite.bi <javascript:;>] > > Sent: Wednesday, September 16, 2015 8:59 AM > > To: dev@oodt.apache.org <javascript:;> > > Subject: Re: Strategy for Closing off GSoC 2015 Work > > > > Hi Val > > > > I've not been involved but I'll attempt to explain. > > > > For communications on some level we use a transport protocol called > XML-RPC > > which allows us to communicate over http using XML, similar to SOAP and > in very > > basic terms REST. Apache Avro is another serialization and transport > > implementation that's far more current and up to date and brings with it > a more > > modern approach and sanity. > > > > Some of us hate XMLRPC with a passion because it has dependencies on some > > crazy stuff, which makes it hard to port bits of Apache OODT else where. > > (Thats just a personal gripe) > > > > Radu has been adding Avro transport alongside the XMLRPC transport so we > can > > test them both out side by side, but in the long run I guess Avro will > become the > > default. > > > > I'm sure Chris, Lewis and Radu can expand on the rambling, but I think > thats the > > high level gist of it. > > > > Tom > > > > On Wed, Sep 16, 2015 at 12:51 PM, Mallder, Valerie < > valerie.mall...@jhuapl.edu <javascript:;>> > > wrote: > > > > > For those of us who have never heard of Avro (maybe it's just me), can > > > you give a quick summary of what it is and what it can be used for? Im > > > sure Radu did a great job and I'm sure it's wonderful, but I'm > clueless. > > > > > > Thanks, > > > Val > > > > > > > > > > > > Sent from my iPhone. > > > ________________________________ > > > From: Lewis John Mcgibbney <lewis.mcgibb...@gmail.com <javascript:;>> > > > Sent: Tuesday, September 15, 2015 11:55:13 PM > > > To: dev@oodt.apache.org <javascript:;>; Radu Manole > > > Subject: Re: Strategy for Closing off GSoC 2015 Work > > > > > > Hi Folks, > > > Further heads up on this. > > > You will have seen quite a bit of traffic on here for commits, etc. > > > We now have 7 of 12 issues resolved. This is a major piece of work and > > > Radu has done extremely well to cover as much of the codebase as he has > > done. > > > We are working to hammer out the final modules now before implementing > > > the AvroRPC implementation with RADIX. > > > Right now, although there is a bunch of unit testing for the AvroRPC > > > implementations (more or less every XMLRPC test is shadowed and > > > implemented to test AvroRPC implementations) the XMLRPC > > > implementations remain the default RPC for all modules. > > > Probably after we can propose this for merging into trunk will we aim > > > to make AvroRPC the default implementation. > > > Thanks for now > > > Lewis > > > > > > On Thu, Sep 3, 2015 at 1:22 AM, Lewis John Mcgibbney < > > > lewis.mcgibb...@gmail.com <javascript:;>> wrote: > > > > > > > I've set up a build for the new branch. > > > > https://builds.apache.org/view/M-R/view/OODT/job/oodt-avro-rpc/ > > > > I'm taking responsibility of keeping it up to date with trunk until > > > > we > > > are > > > > ready to merge into trunk. > > > > Thanks > > > > Lewis > > > > > > > > On Wed, Sep 2, 2015 at 10:52 PM, Lewis John Mcgibbney < > > > > lewis.mcgibb...@gmail.com <javascript:;>> wrote: > > > > > > > >> Hi Tom, > > > >> No probs I'll follow up here when I'm done merging it all in. There > > > >> is quite a bit of code :0| ;) Anyways folks, the new branching > > > >> activity is ongoing at > > > >> http://svn.apache.org/repos/asf/oodt/branches/avro_rpc/ > > > >> I'll follow up here once we are done with it, we can then get some > > > >> serious testing done. > > > >> By the way, just for heads up. In 0.11-SNAPSHOT we intend to mark > > > >> hopefully all of the XMLRPC work as @Deprecated. In 0.12 we will > > > >> then progress with phasing it out entirely and replacing it with > > > >> the AvroRPC implementation. By then we will have it well tested and > > > >> will have built confidence in it all. > > > >> Thanks > > > >> Lewis > > > >> > > > >> On Mon, Aug 31, 2015 at 1:29 PM, Tom Barber > > > >> <tom.bar...@meteorite.bi <javascript:;>> > > > >> wrote: > > > >> > > > >>> Let me know when you've got stuff sorted Lewis, I'm happy to be a > > > >>> XMLRPC-less File Manager guinea pig. > > > >>> > > > >>> Tom > > > >>> > > > >>> On Mon, Aug 31, 2015 at 9:09 PM, Lewis John Mcgibbney < > > > >>> lewis.mcgibb...@gmail.com <javascript:;>> wrote: > > > >>> > > > >>> > ACK > > > >>> > Will do this shortly Chris. > > > >>> > Thanks > > > >>> > > > > >>> > > > > >>> > On Mon, Aug 31, 2015 at 12:58 PM, Mattmann, Chris A (3980) < > > > >>> > chris.a.mattm...@jpl.nasa.gov <javascript:;>> wrote: > > > >>> > > > > >>> > > +1 from me to push this up into a branch. > > > >>> > > > > > >>> > > > > +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > +++++ > > > >>> > > Chris Mattmann, Ph.D. > > > >>> > > Chief Architect > > > >>> > > Instrument Software and Science Data Systems Section (398) > > > >>> > > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > > > >>> > > Office: 168-519, Mailstop: 168-527 > > > >>> > > Email: chris.a.mattm...@nasa.gov <javascript:;> > > > >>> > > WWW: http://sunset.usc.edu/~mattmann/ > > > >>> > > > > +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > +++++ > > > >>> > > Adjunct Associate Professor, Computer Science Department > > > >>> > > University of Southern California, Los Angeles, CA 90089 USA > > > >>> > > > > +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > +++++ > > > >>> > > > > > >>> > > > > > >>> > > > > > >>> > > > > > >>> > > > > > >>> > > -----Original Message----- > > > >>> > > From: Lewis John Mcgibbney <lewis.mcgibb...@gmail.com > <javascript:;>> > > > >>> > > Reply-To: "dev@oodt.apache.org <javascript:;>" < > dev@oodt.apache.org <javascript:;>> > > > >>> > > Date: Thursday, August 27, 2015 at 4:35 PM > > > >>> > > To: "dev@oodt.apache.org <javascript:;>" <dev@oodt.apache.org > <javascript:;>> > > > >>> > > Subject: Re: Strategy for Closing off GSoC 2015 Work > > > >>> > > > > > >>> > > >I'm thinking that we branch trunk and integrate the code > > > >>> > > >(once we > > > >>> rebase > > > >>> > > >properly and compile a list of TODO's) into the branch. > > > >>> > > >I'll be happy to ensure that the branch stays up to date with > > > trunk. > > > >>> > > >This way we can test, stabilize and build confidence in the > > > >>> > > >new > > > >>> remote > > > >>> > > >procedure implementations for various modules. > > > >>> > > >We also still need to build it in to radix so that is a major > > > >>> > > >step > > > >>> as > > > >>> > > >well. > > > >>> > > >Any objections to branching trunk post 0.10 release? > > > >>> > > > > > > >>> > > >On Tuesday, August 25, 2015, Tom Barber > > > >>> > > ><tom.bar...@meteorite.bi <javascript:;>> > > > >>> > wrote: > > > >>> > > > > > > >>> > > >> Yeah I'm well up for getting this all complete xmlrpc in > > > >>> > > >> osgi is > > > >>> > giving > > > >>> > > >>me > > > >>> > > >> a rash. > > > >>> > > >> > > > >>> > > >> The stuff I'm developing I'll happily skip xmlrpc direct to > > > >>> > > >> avro > > > >>> if > > > >>> > it's > > > >>> > > >> functional. > > > >>> > > >> > > > >>> > > >> Tom > > > >>> > > >> On 25 Aug 2015 07:58, "Chris Mattmann" < > > > chris.mattm...@gmail.com <javascript:;> > > > >>> > > >> <javascript:;>> wrote: > > > >>> > > >> > > > >>> > > >> > Agreed. > > > >>> > > >> > > > > >>> > > >> > I am committed to getting this part of the master code > > > >>> > > >> > base in Apache OODT. You’ve done amazing, Radu. > > > >>> > > >> > > > > >>> > > >> > Cheers, > > > >>> > > >> > Chris > > > >>> > > >> > > > > >>> > > >> > — > > > >>> > > >> > Chris Mattmann > > > >>> > > >> > chris.mattm...@gmail.com <javascript:;> <javascript:;> > > > >>> > > >> > > > > >>> > > >> > > > > >>> > > >> > > > > >>> > > >> > > > > >>> > > >> > > > > >>> > > >> > > > > >>> > > >> > -----Original Message----- > > > >>> > > >> > From: Lewis John Mcgibbney <lewis.mcgibb...@gmail.com > <javascript:;> > > > >>> > <javascript:;>> > > > >>> > > >> > Reply-To: <dev@oodt.apache.org <javascript:;> > <javascript:;>> > > > >>> > > >> > Date: Monday, August 24, 2015 at 10:28 PM > > > >>> > > >> > To: "dev@oodt.apache.org <javascript:;> <javascript:;>" > > > >>> > > >> > <dev@oodt.apache.org <javascript:;> > > > >>> > > >> <javascript:;>>, Radu Manole > > > >>> > > >> > <manole.v.r...@gmail.com <javascript:;> <javascript:;>> > > > >>> > > >> > Subject: Strategy for Closing off GSoC 2015 Work > > > >>> > > >> > > > > >>> > > >> > >Hi Folks, > > > >>> > > >> > >As Radu's project is coming to an end, it is wise for us > > > >>> > > >> > >to > > > >>> start > > > >>> > > >> thinking > > > >>> > > >> > >about a strategy for closing off his work. This will > > > >>> > > >> > >involve > > > >>> one or > > > >>> > > >>more > > > >>> > > >> > >of > > > >>> > > >> > >the following and potentially some other tasks. > > > >>> > > >> > > 1) Identifying final TODO's across Review Board, Jira, > > > >>> > Documentation > > > >>> > > >> and > > > >>> > > >> > >Tests. > > > >>> > > >> > > 2) Having the community test this out. Potentially by > > > >>> creating a > > > >>> > > >>branch > > > >>> > > >> > >with the work merged into it accompanied with guidelines > > > >>> > > >> > >for > > > >>> how to > > > >>> > > >>use > > > >>> > > >> > >the > > > >>> > > >> > >work and test out the functionality. > > > >>> > > >> > > 3) Thinking about merging the code into what will soon > > > become > > > >>> OODT > > > >>> > > >> master > > > >>> > > >> > >branch. > > > >>> > > >> > >Any other ideas on top of this? > > > >>> > > >> > >@Radu, > > > >>> > > >> > >I am going through your various issues and will work > > > >>> > > >> > >with > > > >>> Chris and > > > >>> > > >>team > > > >>> > > >> > >to > > > >>> > > >> > >make sure that OODT trunk does not diverge too much from > > > >>> > > >> > >your > > > >>> work. > > > >>> > > >> > >Thank you for your work over the summer. This has been a > > > >>> > challenging > > > >>> > > >> task > > > >>> > > >> > >but one which you've done very well to schedule and > address. > > > >>> > > >> > >On behalf of the OODT community, thank you. > > > >>> > > >> > >Lewis > > > >>> > > >> > > > > > >>> > > >> > >-- > > > >>> > > >> > >*Lewis* > > > >>> > > >> > > > > >>> > > >> > > > > >>> > > >> > > > > >>> > > >> > > > >>> > > > > > > >>> > > > > > > >>> > > >-- > > > >>> > > >*Lewis* > > > >>> > > > > > >>> > > > > > >>> > > > > >>> > > > > >>> > -- > > > >>> > *Lewis* > > > >>> > > > > >>> > > > >> > > > >> > > > >> > > > >> -- > > > >> *Lewis* > > > >> > > > > > > > > > > > > > > > > -- > > > > *Lewis* > > > > > > > > > > > > > > > > -- > > > *Lewis* > > > > -- *Lewis*
