oodt-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From B W <b.du...@gmail.com>
Subject Re: Query-Servlet-XML-RPC
Date Sat, 14 Jan 2012 16:02:10 GMT
Ok.  I'm getting wrapped around the axle.  There is still a Query
architectural component right?  Under http://oodt.apache.org, Query is
listed as a component part.  Is there an up to date architectural diagram
for the apache oodt?

On Fri, Jan 13, 2012 at 11:31 PM, B W <b.dubbu@gmail.com> wrote:

>
>
> On Fri, Jan 13, 2012 at 7:58 PM, Mattmann, Chris A (388J) <
> chris.a.mattmann@jpl.nasa.gov> wrote:
>
>> Hi BW,
>>
>> On Jan 13, 2012, at 9:54 AM, B W wrote:
>>
>> >>
>> >> The QueryServer used to be a component that was seeded with a set of
>> initial Profile Server
>> >> endpoints, and then used those Profile Server end points to crawl a
>> directed graph of resources,
>> >> either automatically or interactively. As it consumed the resources,
>> it looked for:
>> >>
>> >> * Other Profile Servers -- to add more nodes to crawl (pointed at
>> other resources)
>> >> * Product Servers -- to download and package products from
>> >> * raw URLs -- to download and package products from
>> > So, it doesn't do this anymore?
>>
>> Well, it doesn't exist anymore. There is not more official QueryServer
>> component (formerly called
>> "edm-query") that is part of the Apache OODT software.
>>
>> So, the Query Service is now just apart of REST architectural aspect?
>
>>  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.mattmann@nasa.gov
>> WWW:   http://sunset.usc.edu/~mattmann/
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Adjunct Assistant Professor, Computer Science Department
>> University of Southern California, Los Angeles, CA 90089 USA
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message