> <You_said>With MTS and COM+ specifically, CF can't declare a > "transactional page" like ASP can, so you'll lose some transaction > functionality.</You_said> > > In my limited understanding of MTS, I think this is when an ASP > pages declares itself as the base MTS client. Have you hit this > problem in practice and determined a work around? Maybe you could > create a proxy base MTS client and pass all object calls through > this (sounds a bit of a mung) ? > > Perhaps Allaire are fixing these issues for a subsequent release > of CF. > > I'd like to be able to use the powerful features of n-tier dev > without having to go back to ASP. I've never needed to use the transactional capabilities of MTS - my use for it has been for efficiency in object brokering. So, I've never missed that functionality. Typically, for transactional purposes, we try to move that functionality directly to the database. I understand that there are instances where that's not optimal, and I also understand that in the traditional n-tier model transactions are typically handled in the object tier, but I think you get better performance and reliability by doing that in the database whenever possible. As for whether CF will support MTS/COM+ transactional capabilities in the future, I wouldn't hold my breath. On the other hand, it will certainly support Java transactional standards such as JTS. 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
