<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel rdf:about="http://blogmarks.net/api/user/kasi77/marks/tag/load,email">
<title>Public marks from user kasi77 with tags load &amp; email</title>
<description>Public marks from user kasi77 with tags load &amp; email</description>
<link>http://blogmarks.net/user/kasi77/marks/tag/load,email</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/kasi77/mark/1058261427"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/kasi77/mark/1058261427">
<title>10 historical software bugs with extreme consequences | Royal Pingdom</title>
<link>http://royal.pingdom.com/2009/03/19/10-historical-software-bugs-with-extreme-consequences/</link>
<description>One of the latest software errors that had widely noticed consequences was Google’s Gmail outage in February. The problem in that case was, according to Google, a bug in the software that distributed load between its different data centers.

The Gmail outage only resulted in people not having access to their email for a few hours. No one got killed. Nothing exploded. It was an inconvenience, and while it was a significant inconvenience for some of Gmail’s users, it was still just that: an inconvenience.

This article is about some of the more dire consequences of software errors through the years. Incidents that make the Gmail outage seem rather trivial.</description>
<dc:date>2009-04-05T19:11:18Z</dc:date>
<dc:author>kasi77</dc:author>
<dc:subject>software, load, email, gmail, it, bug</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://royal.pingdom.com/2009/03/19/10-historical-software-bugs-with-extreme-consequences/"><img border="0" src="http://blogmarks.net/screenshots/2009/04/05/ce0e604ac851c7e71feaf1730e58a26c.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://royal.pingdom.com/2009/03/19/10-historical-software-bugs-with-extreme-consequences/">10 historical software bugs with extreme consequences | Royal Pingdom</a></h4>
 
by <a href="http://blogmarks.net/user/kasi77">kasi77</a> 
<p class="description">One of the latest software errors that had widely noticed consequences was Google’s Gmail outage in February. The problem in that case was, according to Google, a bug in the software that distributed load between its different data centers.

The Gmail outage only resulted in people not having access to their email for a few hours. No one got killed. Nothing exploded. It was an inconvenience, and while it was a significant inconvenience for some of Gmail’s users, it was still just that: an inconvenience.

This article is about some of the more dire consequences of software errors through the years. Incidents that make the Gmail outage seem rather trivial.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/software">software</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/load">load</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/email">email</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/gmail">gmail</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/it">it</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/bug">bug</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058261427">Copy</a> | 
<a href="http://blogmarks.net/link/3144363">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>