> Do you have an idea of how often the problems with specific
> datatypes expected by COM object occurs in practice ?
It's been relatively infrequent in my experience. If you're writing your own
COM objects, which you would be if you were building your own n-tier app,
you could write them in a way that would avoid any problems.
> Also it would be useful to know in advance exactly what kind
> of trouble we can expect from ".. dealing with object hierarchies."
This is primarily a difficulty with interfaces provided by the operating
system, such as ADSI. You generally can't use them effectively from
CFOBJECT.
> Are there any work arounds for these kind of issues such as
> wrapping the COM object in a VB adaptor?
You can write wrappers to address any of these problems, but wrappers will
affect performance. This wouldn't be an issue for applications built to
manage the interfaces mentioned above, but it would be for n-tier apps.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
