Does this skeleton code look like a good start for a ECC patterned class
design?  I was thinking of dropping the Engine and just putting the Object
management methods into the Collection object.  Comments and ideas
welcomed...

Francesco



namespace pr2002.DataDesign
{

  public interface IBusinessObject : IDisposable
  {
  }

  class Person : IBusinessObject
  {
    public void Dispose()
    {
    }
  }

  public interface IBusinessObjectCollection : IDisposable
  {
  }

  class PersonCollection : System.Collections.CollectionBase,
IBusinessObjectCollection
  {
    public void Dispose()
    {
    }
  }

  public interface IBusinessObjectEngine : IDisposable
  {
  }

  class PersonEngine : IBusinessObjectEngine
  {
    public void Dispose()
    {
    }
  }

} // end DataDesign Namespace

_________________________________________________________________
Join the world�s largest e-mail service with MSN Hotmail.
http://www.hotmail.com

You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced 
DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.

Reply via email to