Garrett D'Amore writes: > #1: This is a fast track. If we are going to start insisting that the > project team make significant changes to the project (especially changes > to which the project team doesn't readily agree), then the project > should probably be derailed.
True; but I don't think we're quite at that point yet. > #3: I propose that in the meantime, the TSS API be reduced to > Consolidation Private binding, if not already at that level. Since > there are no consumers yet, this seems fairly reasonable and unlikely to > cause undue harm to projects. I disagree. The API is already a standard item, and making it private is just going to lead to unnecessary confusion. The problem here hasn't been with the existence or stability of the API, but rather the internal design's usefulness in (and conformance to) Zones. The two should be separate. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
