Jeff, Thanks.
> why not use an inheritance hierarchy to abstract out common functionality? Yes. Good point; in many cases this would be simpler. Generally I try to design with composition rather than inheritance whenever possible, so the obvious escaped me :). As to decoupling the model from the controller--I have already elected to do that (passing the whole controller down makes me a little uncomfortable) so using inheritance will work fine for me. Thanks again, John-Mason Shackelford Software Developer NCS Pearson - Measurement Services 2510 North Dodge St. Iowa City, IA 52245 319-354-9200x6214 [EMAIL PROTECTED] **************************************************************************** This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network. **************************************************************************** ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en [INVALID FOOTER]
