RE: Concurrency issue
- From: stcheng@xxxxxxxxxxxxxxxxxxxx (Steven Cheng [MSFT])
- Date: Wed, 02 Jul 2008 09:23:53 GMT
Hi Varde,
Have you got any progress on this issue or does the information in my last
reply help you some?
If you have any further specific questions, please feel free to post here.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@xxxxxxxxxxxxxx
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
From: stcheng@xxxxxxxxxxxxxxxxxxxx (Steven Cheng [MSFT])
Organization: Microsoft
Date: Mon, 30 Jun 2008 03:31:20 GMT
Subject: RE: Concurrency issue
f
Hi Varde,
Regarding on the data editing/updating question you mentioned, it is
actually related to the Data Accessing's concurrent violation handling
topcs. No matter you're dealing with data in ASP.NET or desktop
application, as long as the data is potentially be updated by multiple
client concurrently, we will have to consider such issues.
In .NET framework, we'll consider handling such concurrent violation at
ADO.NET layer. Here are some web articles mentioned some general ideas and
concepts:
#Handling Data Concurrency Using ADO.NET
http://msdn.microsoft.com/en-us/magazine/cc163924.aspx
#Concurrent Model in ADO.NET
http://www.codeguru.com/csharp/.net/net_data/datagrid/article.php/c12969/
Also, in the ASP.NET Data Accesss tutorial, I also find the following one
which is focus on the concurrency handling demonstration:
#Implementing Optimistic Concurrency
http://www.asp.net/Learn/data-access/tutorial-21-cs.aspx
You'll find that the common approach is always compare all the fields of
the record when performing update into database so as to avoid overwrite
the other ones' changes. And the ADO.NET layer can capture such concurrent
error.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@xxxxxxxxxxxxxx
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#noti
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
.
- Follow-Ups:
- RE: Concurrency issue
- From: A. Varde
- RE: Concurrency issue
- Prev by Date: Re: Custom Validator and ServerValidateEventArgs
- Next by Date: Re: How to obtain radiobutton value from a GridView
- Previous by thread: Custom Validator and ServerValidateEventArgs
- Next by thread: RE: Concurrency issue
- Index(es):