> Does anyone know the implications of using coldfusion as
> opposed to ASP to interact with MTS and COM. What are the
> advantages/disadvantages of using ColdFusion when calling
> COM or MTS registered components in a middle tier environment?
ColdFusion can be used as a COM/MTS/COM+ client. It doesn't work quite as
well as ASP for this, but this is balanced by the ease of development for
all the other parts.
Typically, CF can be used with COM objects, although there are some things
it can't do (or can't do especially well). If a specific COM object expects
a value passed to it to be a specific datatype, and that object doesn't do
an implicit cast, you may have problems. For example, the properties and
methods of some objects expect hexadecimal values, and CF can't pass those
values in a way that the object will be able to use.
CF also has trouble when dealing with object hierarchies. Many common COM
interfaces, such as ADSI, CDO and WMI, expose hierarchies of objects; it's
difficult to use CF with them.
With MTS and COM+ specifically, CF can't declare a "transactional page" like
ASP can, so you'll lose some transaction functionality. Other than that, the
way CF talks to MTS/COM+ components isn't any different than how it talks to
"regular" COM objects.
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
