|
-
distributed transactions failover - .NET components
Hi
Suppose i have an application built with .NET components and the components
participate in some distributed transactions and messaging services and this
is specified in the components through transaction attributes. and these
components are registered with COM+.
now the question is...
is it still possible to change the transaction attributes through the com+
serrvices console? i mean, once i specify the transaction attributes in the
.net component code, can i still change them through the com+ serrvices snap-in?
Also, how is failover handled in such a scenario. if we are having this application
deployed in a clustered environment, what happens when a primary node in
a cluster goes down and a transaction is in progress? will the transaction
continue on the secondary node in the cluster?
please comment.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
Forum Rules
|
Top DevX Stories
Easy Web Services with SQL Server 2005 HTTP Endpoints
JavaOne 2005: Java Platform Roadmap Focuses on Ease of Development, Sun Focuses on the "Free" in F.O.S.S.
Wed Yourself to UML with the Power of Associations
Microsoft to Add AJAX Capabilities to ASP.NET
IBM's Cloudscape Versus MySQL
|
Bookmarks