Hmm, I think this is very domain-specific, and would easily fit in that 20% that we turn our blind eye not to complicate the other 80%. Anyway, your proposed solution seems to be non-intrusive enough that most users would never need to know about this, and goes well in concert with the already existing Orderer class (which I never noticed. Doh).
-- Marcus Brito On Sun, 25 Jul 2004 09:39:49 -0400, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > I thought of this while working on the new Panorama example code. > > A sizable chunk of code in the service exists to get the contributed > tasks into the right order, based on pre- and post-requisites: --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
