Right.

I understood about classes while for the
interface concept I think is right to aggregate
the "Descriptor" property,isnt it ?

Rogers, thank You very much for your answers.

On Mon, 27 Nov 2000 23:11:05 +0100, "antonio mantuano"

Sure, you could use interfaces. I don't know whether it is warranted,
though. Again it depends on your design scenario.
We've already determined that your classes A and B are not the same
"thing" in the problem domain. Let me ask you another question: would
you ever want to perform an operation on the Descriptor property of
any class, regardless of its class type?
--
Rick Rogers (TeamB); Fenestra Technologies, http://www.fenestra.com/
  Use Borland servers; posts via others are not seen by TeamB.
  For more info, see http://www.borland.com/newsgroups/genl_faqs.html

Yes, it's true. My application has some classes designed to three main
utilizations :
1. classes 'element' : their instances contain attributes loaded from
various relational tables.
2. classes 'type of' : their instances are the type descriptor of classes of
the first point.
3. classes 'collection' : their instances are designed to maintenate the
instance of classes of
    1th and 2nd  types of ones.

well, I won't that the client app of my server app sees all the structure
above , but only
a set of interfaces  ( DCOM/CORBA ) then when a client request a
"Descriptor" of
a interface  I return ,behind the scene ( !! ), return a string from any
classes.

Truly, I don't understood if :
1. I well designed the classes.
2. I well designed the interfaces.
3. I know the DCOM services , I see the MIDAS doesn't cover my needed.

Excuse me fo my bad english.
Thank you .

On Tue, 28 Nov 2000 12:01:32 +0100, "antonio mantuano"

Okay, then I would use an IDescriptor interface.
--
Rick Rogers (TeamB); Fenestra Technologies, http://www.fenestra.com/
  Use Borland servers; posts via others are not seen by TeamB.
  For more info, see http://www.borland.com/newsgroups/genl_faqs.html