Hi William, I have a few comments/questions.
- Section 3: Solution, Overview: "The Validator method of the disk object will perform the validation prior to instantiation" What does this mean? Since this is one of the method in the disk object, doesn't the object need to be instantiated first, and then, call the validator to validate after all the values are filled in? - Validation issue reporting: Would it be adhere more to the "object-oriented" style if you throw an exception that contains all the information you will be reporting back to the caller. - Section 4, can you elaborate on the first use case? I am not quiet sure how is the validation work for ZFS pools distributed over several disks. Will there be validation done on a list of disk objects in this case? Thanks, --Karen On 02/12/10 06:53, William Schumann wrote: > Posted design document for the Validator, which I refer to as the Disk > Layout Validator, for initial review. > > http://hub.opensolaris.org/bin/view/Project+caiman/CUE_docs > Caiman Unified Engine Disk Layout Validator(.odt) > <http://hub.opensolaris.org/bin/download/Project+caiman/CUE_docs/CUDvalidator.odt> > > Thank you, > William > > > _______________________________________________ > caiman-discuss mailing list > caiman-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/caiman-discuss/attachments/20100216/a591f752/attachment-0001.html>
