On Sat, Jan 14, 2012 at 6:45 PM, Mattmann, Chris A (388J) < [email protected]> wrote:
> Hi BW, > > On Jan 14, 2012, at 4:53 PM, B W wrote: > [...snip...] > > >>> > >>> Has there been architectural re-factoring to address this? > >> > >> Actually nope, it's still missing but something that we typically > mitigate > >> through > >> careful design and deployment strategies with the system. Overall it > would > >> be nice > >> to have GLIDE-like properties integrated into the OODT core, but that > >> hasn't been > >> done yet. > >> > >> Uug..Ok. > > Where in the current design is the tight coupling? > > No-where really -- it's just that we don't have an explicit representation > of an > architecture object in Apache OODT proper, as it existed in GLIDE (being > built on top of PRISM-MW it afforded us the ability for architectural > introspection, etc.) > > You mean the the tight coupling is a real characteristic but conceptual at the messaging component that does not really exists as a concrete artifact? > > > > Can you talk to the the strategies for mitigation? > > > There haven't really been any as of yet IIUC. It's just on someone's TODO > eventually > (hopefully) to look at that type of redeployment capability in the future. > > Cheers, > Chris > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Chris Mattmann, Ph.D. > Senior Computer Scientist > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > Office: 171-266B, Mailstop: 171-246 > Email: [email protected] > WWW: http://sunset.usc.edu/~mattmann/ > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Adjunct Assistant Professor, Computer Science Department > University of Southern California, Los Angeles, CA 90089 USA > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >
