<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Vdiscussion &#187; Uncategorized</title>
	<atom:link href="http://vdiscussion.com/category/uncategorized/feed/" rel="self" type="application/rss+xml" />
	<link>http://vdiscussion.com</link>
	<description>Vinoth Kumar&#039;s Discussion</description>
	<lastBuildDate>Wed, 09 Dec 2009 15:34:03 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Explain about Database Concurrency Issues</title>
		<link>http://vdiscussion.com/explain-about-database-concurrency-issues/</link>
		<comments>http://vdiscussion.com/explain-about-database-concurrency-issues/#comments</comments>
		<pubDate>Mon, 16 Nov 2009 14:27:38 +0000</pubDate>
		<dc:creator>ma.vinothkumar</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[ADO.NET]]></category>
		<category><![CDATA[Database]]></category>
		<category><![CDATA[Database Concurrency]]></category>
		<category><![CDATA[RDBMS]]></category>
		<category><![CDATA[Relational Database Management System]]></category>

		<guid isPermaLink="false">http://vdiscussion.com/?p=85</guid>
		<description><![CDATA[When multiple users try to update a single record at the same time, you will have concurrency issues. In a single-tier application, this is never an issue because there is only one user accessing data. In a two-tier system, you as the developer have the option of implementing either pessimistic or optimistic locking—however, this depends [...]]]></description>
			<content:encoded><![CDATA[<p>When multiple users try to update a single record at the  same time, you will have concurrency issues. In a single-tier application, this  is never an issue because there is only one user accessing data. In a two-tier  system, you as the developer have the option of implementing either pessimistic  or optimistic locking—however, this depends on the Relational Database  Management System (RDBMS) because not all databases support optimistic locking.  In most two-tier applications, you are always connected to the database when you  are reading and writing data. If you set up pessimistic concurrency, when one  user is trying to update a record, no other user can update the record at the  same time (they will receive an error message explaining that the record is  locked). If you implement optimistic concurrency, you will have to write code to  handle the occurrence of one user updating a record that is not current. In a  three-tier application, the developer must always handle database updates  because no connection is maintained with the database. In most cases, this  applies to a well-written two-tier application as well.</p>
<p>Microsoft&#8217;s new database access technology, ADO.NET, can help  to make many of these issues easier to solve—but even ADO.NET will only throw an  exception saying that someone else has updated the record. It is still up to the  developer to handle this situation, and it is rarely solved the same way on any  two applications. How you handle this situation depends mostly on what the users  want.</p>
]]></content:encoded>
			<wfw:commentRss>http://vdiscussion.com/explain-about-database-concurrency-issues/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What is XML ?</title>
		<link>http://vdiscussion.com/what-is-xml/</link>
		<comments>http://vdiscussion.com/what-is-xml/#comments</comments>
		<pubDate>Thu, 12 Nov 2009 12:24:37 +0000</pubDate>
		<dc:creator>ma.vinothkumar</dc:creator>
				<category><![CDATA[Theory Subjects]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[XML]]></category>
		<category><![CDATA[HTML]]></category>
		<category><![CDATA[SGML]]></category>
		<category><![CDATA[W3C]]></category>

		<guid isPermaLink="false">http://vdiscussion.com/?p=42</guid>
		<description><![CDATA[XML stands for Extensible Markup Language, was defined by the XML Working Group of the World Wide Web Consortium (W3C). This group described the language as follows: The Extensible Markup Language (XML) is a subset of SGML&#8230;Its goal is to enable generic SGML to be served, received, and processed on the Web in the way [...]]]></description>
			<content:encoded><![CDATA[<p>XML  stands for Extensible Markup Language, was defined by the<br />
XML Working Group of the World Wide Web Consortium (W3C). This group<br />
described the language as follows:<br />
The Extensible Markup Language (XML) is a subset of SGML&#8230;Its<br />
goal is to enable generic SGML to be served, received, and processed<br />
on the Web in the way that is now possible with HTML. XML has been<br />
designed for ease of implementation and for interoperability with both<br />
SGML and HTML.</p>
<p>As you can see, XML is a markup language designed specifically for delivering<br />
information over the World Wide Web, just like HTML (Hypertext Markup<br />
Language), which has been the standard language used to create Web pages<br />
since the inception of the Web. Since we already have HTML, which continues<br />
to evolve to meet additional needs, you might wonder why we require a com-<br />
pletely new language for the Web.</p>
]]></content:encoded>
			<wfw:commentRss>http://vdiscussion.com/what-is-xml/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
