<?xml version='1.0' encoding='ISO-8859-1'?>
<!DOCTYPE rss PUBLIC '-//Netscape Communications//DTD RSS 0.91//EN'
              'http://my.netscape.com/publish/formats/rss-0.91.dtd'>
<rss version='0.91'>
   <channel>

   <title>Sigona Golf Club</title>
   <link>http://www.sigonagolf.com</link>
   <description>Your portal to the golfing world</description>
   <language>en-us</language>

   <copyright>Copyright 2011, Sigona Golf Team.</copyright>
   <managingEditor>me</managingEditor>
   <webMaster>wm</webMaster>

      <image>
        <title>sigona</title>
        <url>http://www.sigonagolf.com/images/toplogo.png</url>

        <link>www.sigonagolf.com</link>
        <width>88</width>
        <height>31</height>
        <description>General Updates on Sigona Golf Club</description>
      </image>


					
				<item>
				<title>Quote of The Day</title>
				<link>http://www.sigonagolf.com</link>
				<description>Golf is cool. Concurrency control is necessary so as to gain the speeds that cannot be found in sequential systems, without the breach of integrity.</description>
				</item>
				
				<item>
				<title>Events</title>
				<link>http://www.sigonagolf.com</link>
				<description>Party at Sigona.</description>
				</item>
				
				<item>
				<title>Lets see if it works</title>
				<link>www.blah.com</link>
				<description>Purely sequential (serial) transactions with no overlapping over time have consistency but are too slow and impractical for distributed systems. On the other hand, if concurrent transactions with interleaving operations are allowed in an uncontrolled manner, unexpected result may be yielded such as the lost update problem, the dirty read problem and the incorrect summary problem. Concurrency control is necessary so as to gain the speeds that cannot be found in sequential systems, without the breach of integrity.</description>
				</item>
				
</channel>
</rss>

