Hi Jacek, The way we should handle that is that the Ingest Service will be created as an interface object in the model, then we will add Start and Stop operations to that object. No need to expand the component diagram.
In general, a "service" (not a UML term) will have one or more interface objects that provide the service, and each interface will have one or more operations (i.e. member functions in C++ terminology, methods in Java terms). Jeff > From: Jacek Becla <[EMAIL PROTECTED]> > Organization: Stanford Linear Accelerator Center > Reply-To: LSST Data Management <[email protected]> > Date: Fri, 17 Mar 2006 12:14:26 -0800 > To: LSST Data Management <[email protected]> > Subject: [LSST-data] Ingest related questions > > Keywords: MiddleWG > > Ray/Jeff > > A couple of questions related to APIs for the Catalog > Ingest at the Base Camp.: > > > On the component diagram I don't see anything regarding > starting Ingest Service. Who should control (start/stop) > Ingest Service? Should we add this missing link to the diagram? > > > How to exchange data between Pipeline and IngestDataConverter? > Through a named pipe? (BTW, can you think of a better name > for the Converter that will convert binary data from pipeline > into ascii file for ingest) > > > How should Ingest Service detect new input files? > Should we 'trigger' loading, or the Ingest Service > should periodically scan the contents of a directory? > (triggering would reduce delay) > > Thanks, > Jacek > > > _______________________________________________ > LSST-data mailing list > [email protected] > http://www.lsstmail.org/mailman/listinfo/lsst-data > _______________________________________________ LSST-data mailing list [email protected] http://www.lsstmail.org/mailman/listinfo/lsst-data
