"Doug Turner" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > If you mean a collection of objects found by a module, that requirement > is easier to swallow - although it would be impossible to enforce.
This is what I meant, I was just calling it by the generic term component. I work with XPCOM in a server environment. In this environment we are looking at building a SOAP server. I wanted to write a tool to generate the WDSL files. To do this I need to know what interfaces the objects in the module support. In another conversation I was talking to a Transformiix developer about adding extension functions via XPCOM. This ended up being a second case of needing a list of interfaces. After thinking about it further I realized that you couldn't build a visual IDE editor tool with this ability either. Next I opened up OLEView and looked at some MS typelibs. It looks to me like MS typelibs contain the list of interfaces (OLEView searches for them too when a typelib is not found). XPCOM has interface files instead of typelibs. This makes me think that MSCOM has this ability while XPCOM does not. Finally I got concerned about getting thousands of components out there without the ability to list their interfaces and the legacy problems this would cause when things like an IDE get developed at a later date. -- Jon Smirl [EMAIL PROTECTED]
