<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://franklynch.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Latest News from Frank Lynch</title>
 <link>http://franklynch.sys-con.com/</link>
 <description>Latest News from Frank Lynch</description>
 <language>en</language>
 <copyright>Copyright 2009 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Fri, 04 Dec 2009 17:44:38 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>360</ttl>
<item>
 <title>Where HTTP Fails SOAP</title>
 <link>http://franklynch.sys-con.com/node/114115</link>
 <description>Web services allow for the delivery of SOAP messages over any protocol. A common misconception is that all SOAP messages must be transmitted over HTTP. While that approach is useful in many cases, there are situations where it makes sense to use alternatives. This paper investigates situations where HTTP does not scale sufficiently for enterprise Web service deployments and looks at available alternatives.&lt;p&gt;&lt;a href=&quot;http://franklynch.sys-con.com/node/114115&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Sun, 23 Oct 2005 12:45:00 EDT</pubDate>
 <guid isPermaLink="true">http://franklynch.sys-con.com/node/114115</guid>
 <comments>http://franklynch.sys-con.com/node/114115#feedback</comments>
</item>
</channel>
</rss>
