Hello all, I "seeded" a few example interface objects into the domain model, Middleware API package. There is an abstract interface called Service, and a specialized interface called Event Service. This reflects the type of interface that I anticipate would run as a service.
On the other hand, there is an interface called Pipeline Creation, that is probably more of an invocation interface running bound inside a tool or application. (This is admittedly an arbitrary design choice, we could do it as a service as well). Anyway, I have proposed certain operations on these interfaces, with parameters, based on what I know. I added a new Domain entity class as well, called Event Channel, which I felt was needed (but have not moved it into the Framework package yet) as a parameter to certain Event Service operations. We should try to flesh this package out as much as possible prior to the robustness exercise in Los Angeles. Thanks! Jeff _______________________________________________ LSST-data mailing list [email protected] http://www.lsstmail.org/mailman/listinfo/lsst-data
