<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://marklittle.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Latest News from Mark Little</title>
 <link>http://marklittle.sys-con.com/</link>
 <description>Latest News from Mark Little</description>
 <language>en</language>
 <copyright>Copyright 2009 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Wed, 09 Dec 2009 01:22:27 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>360</ttl>
<item>
 <title>Stateful Interactions in Web Services</title>
 <link>http://marklittle.sys-con.com/node/44675</link>
 <description>In July 2003 a consortium of Web services vendors released the Web services Composite Application Framework (WS-CAF) to the community. WS-CAF is comprised of three specifications that together provide a means of reliably composing individual Web services into larger aggregate applications.&lt;p&gt;&lt;a href=&quot;http://marklittle.sys-con.com/node/44675&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 30 Apr 2004 00:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://marklittle.sys-con.com/node/44675</guid>
 <comments>http://marklittle.sys-con.com/node/44675#feedback</comments>
</item>
<item>
 <title>Introducing WS-CAF - More than just transactions</title>
 <link>http://marklittle.sys-con.com/node/39936</link>
 <description>Web services have become the integration platform of choice for enterprise applications. Those applications by the very nature of their enterprise-scale components can be complex in structure, which is compounded by the need to share common data or context across business processes supported by those applications.&lt;p&gt;&lt;a href=&quot;http://marklittle.sys-con.com/node/39936&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Mon, 01 Dec 2003 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://marklittle.sys-con.com/node/39936</guid>
 <comments>http://marklittle.sys-con.com/node/39936#feedback</comments>
</item>
<item>
 <title>Introducing WS-Transaction  Part 1</title>
 <link>http://marklittle.sys-con.com/node/39769</link>
 <description>In July 2002, BEA, IBM, and Microsoft released a trio of specifications designed to support business transactions over Web services. These specifications, BPEL4WS, WS-Transaction, and WS-Coordination, together form the bedrock for reliably choreographing Web services-based applications, providing business process management, transactional integrity, and generic coordination facilities respectively.&lt;p&gt;&lt;a href=&quot;http://marklittle.sys-con.com/node/39769&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 23 May 2003 00:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://marklittle.sys-con.com/node/39769</guid>
 <comments>http://marklittle.sys-con.com/node/39769#feedback</comments>
</item>
<item>
 <title>Introducing WS-Coordination</title>
 <link>http://marklittle.sys-con.com/node/39751</link>
 <description>In July 2002, BEA, IBM, and Microsoft released a trio of specifications designed to support business transactions over Web services. These specifications - BPEL4WS, WS-Transaction, and WS-Coordination - together form the bedrock for reliably choreographing Web services-based applications, providing business process management, transactional integrity, and generic coordination facilities respectively.&lt;p&gt;&lt;a href=&quot;http://marklittle.sys-con.com/node/39751&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Tue, 22 Apr 2003 00:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://marklittle.sys-con.com/node/39751</guid>
 <comments>http://marklittle.sys-con.com/node/39751#feedback</comments>
</item>
<item>
 <title>Business Transaction Protocol: Transactions for a New Age</title>
 <link>http://marklittle.sys-con.com/node/39607</link>
 <description>Use of atomic transactions is a well-known technique for guaranteeing consistency in the presence of failures. The ACID properties of atomic transactions (Atomicity, Consistency, Isolation, Durability) ensure that even in complex business applications consistency of state is preserved.&lt;p&gt;&lt;a href=&quot;http://marklittle.sys-con.com/node/39607&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Mon, 21 Oct 2002 00:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://marklittle.sys-con.com/node/39607</guid>
 <comments>http://marklittle.sys-con.com/node/39607#feedback</comments>
</item>
<item>
 <title>The Business Transaction Protocol: Transactions for a New Age</title>
 <link>http://marklittle.sys-con.com/node/39578</link>
 <description>Atomic transactions are a well-known technique for guaranteeing consistency in the presence of failures. The ACID properties of atomic transactions ensure that, even in complex business applications, consistency of state is preserved.&lt;p&gt;&lt;a href=&quot;http://marklittle.sys-con.com/node/39578&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Mon, 23 Sep 2002 00:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://marklittle.sys-con.com/node/39578</guid>
 <comments>http://marklittle.sys-con.com/node/39578#feedback</comments>
</item>
<item>
 <title>End-to-End Transactionality</title>
 <link>http://marklittle.sys-con.com/node/36883</link>
 <description>In addition, it was suggested that traditional Online Transaction Processing systems (OLTP) don&amp;#8217;t suffer from such limitations, rendering them more suitable for the emerging e-commerce applications that may require such guarantees.&lt;p&gt;&lt;a href=&quot;http://marklittle.sys-con.com/node/36883&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 01 Mar 2002 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://marklittle.sys-con.com/node/36883</guid>
 <comments>http://marklittle.sys-con.com/node/36883#feedback</comments>
</item>
</channel>
</rss>
