Class vs Component

  • Thread starter Thread starter Randy L.
  • Start date Start date
R

Randy L.

I was curious as to the curent best practices for data sharing within NET
2.0 Smart Clients.

Typically I have have isolated data/datasets, webservices interaction, file
IO, etc. using the Component class (IComponent), relying heavily on the
sharing capabilities it provides. The entire application would see this as
it single source for data interaction. They used much the same approach with
the IssueVision NET 1.1 sample application.

Is this still a "best practices" approach or have changes in NET 2.0 negated
this type of approach.

Thanks,
Randy L.
 
It's difficult to tell from what you posted whether it is a "best
practice". To me, best practices are essentially patterns, and if you
look at the literature that is well known for OO patterns both from a
decade ago and current day, you will find that often the context governs
the patterns that are used.

Without more detailed description of 1. the challenges you face and 2.
the visions of the app as far as extensibility and scalability are
concerned, it would be very difficult to recommend any particular pattern.

Regards

John Parrish
 
Back
Top