Fair enough I'll leave it those who know! (Still just continuing on my quest to dump XML-RPC and run for the hills! ;) )
I also don't want Radu's stuff just get forgotten about or so out of sync its wasted, especially as you're talking about OODT 2 when we haven't even got 1 shipped yet! ;) On Wed, Nov 4, 2015 at 4:37 PM, Chris Mattmann <chris.mattm...@gmail.com> wrote: > Yes, they are interfaced up. No it’s not a simple pick and > choose everywhere since the parts for selecting the underlying > transport are sometimes configurable, and other times hard coded > last I looked. > > Also I think we can effectively split and simply not interface this > and leave 1.x and 0.x as the XML-RPC lines, and eventually deprecate > XML-RPC in 2.x (Avro) and just move to an Avro only thing. Maintaining > both and having the communication layer interfaced up is a nightmare. > > My 2c. > > Cheers, > Chris > > — > Chris Mattmann > chris.mattm...@gmail.com > > > > > > > -----Original Message----- > From: Tom Barber <tom.bar...@meteorite.bi> > Reply-To: <dev@oodt.apache.org> > Date: Wednesday, November 4, 2015 at 8:34 AM > To: "dev@oodt.apache.org" <dev@oodt.apache.org> > Subject: Re: Avro RPC stuff > > >Booo! > > > >Aren't they just interfaced up and you pick either XMLRPC or Avro? > > > > > > > >On Wed, Nov 4, 2015 at 4:31 PM, Chris Mattmann <chris.mattm...@gmail.com> > >wrote: > > > >> Hey Guys, > >> > >> IMO this is a post 1.0 Apache OODT release. > >> I’d like to do a full triage of e.g., the OODT-491 > >> stuff, get as much of that committed as possible; > >> also the typing stuff for File Manager, and a couple > >> other bells and whistles. > >> > >> This will fundamentally change and is backwards non-compat > >> if we move to Avro. For example an 0.x and/or 1.x OODT > >> client or server won’t be able to talk to a 2.x OODT Avro > >> client/server. > >> > >> Also this needs to be tested e.g, in an ImageCat, DRAT, > >> and/or mission scenario to make sure it fully works as > >> expected before a merge into master. > >> > >> Cheers, > >> Chris > >> > >> — > >> Chris Mattmann > >> chris.mattm...@gmail.com > >> > >> > >> > >> > >> > >> > >> -----Original Message----- > >> From: Lewis John Mcgibbney <lewis.mcgibb...@gmail.com> > >> Reply-To: <dev@oodt.apache.org> > >> Date: Wednesday, November 4, 2015 at 8:25 AM > >> To: "dev@oodt.apache.org" <dev@oodt.apache.org> > >> Subject: Re: Avro RPC stuff > >> > >> >The Pom.xml rearranging screwed me a few weeks back. > >> >I've got a patch locally to sort this ot and will commit then drag the > >> >avro > >> >RPC branch up to date with trunk. > >> >What we need to do is properly scope out what needs to be done to > >>finish > >> >this task off. > >> >Radu, > >> >Are you able to write here what you think is required to finish the > >>task > >> >off please? > >> >Thanks > >> > > >> >On Wednesday, November 4, 2015, Tom Barber <tom.bar...@meteorite.bi> > >> >wrote: > >> > > >> >> Hey Lewis/Radu > >> >> > >> >> Where are we on this? Anything I can do to help drag it into the > >>land of > >> >> the living? > >> >> > >> >> Tom > >> >> > >> > > >> > > >> >-- > >> >*Lewis* > >> > >> > >> > > >
