<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://jordananastasiade.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Latest News from Jordan Anastasiade</title>
 <link>http://jordananastasiade.sys-con.com/</link>
 <description>Latest News from Jordan Anastasiade</description>
 <language>en</language>
 <copyright>Copyright 2009 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Mon, 07 Dec 2009 15:30:28 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>360</ttl>
<item>
 <title>Optimizing Web Services Using Java, part II - Increased flexibility, reusability, and power</title>
 <link>http://jordananastasiade.sys-con.com/node/39952</link>
 <description>In the first article of this series (WSJ, Vol. 3, issue 12), I described generic Java and examined the issues involved in supporting variant generic types in Java. That article also explained how generic variant types increase the readability, maintainability, and safety of our code.&lt;p&gt;&lt;a href=&quot;http://jordananastasiade.sys-con.com/node/39952&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Wed, 31 Dec 2003 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://jordananastasiade.sys-con.com/node/39952</guid>
 <comments>http://jordananastasiade.sys-con.com/node/39952#feedback</comments>
</item>
<item>
 <title>Optimizing Web Services Using Java, Part I - Generic Java and Web services</title>
 <link>http://jordananastasiade.sys-con.com/node/39935</link>
 <description>What lies behind Web services? Some say the answer depends on the power of the language used in the implementation, in addition to known standards like XML, SOAP, and WSDL.&lt;p&gt;&lt;a href=&quot;http://jordananastasiade.sys-con.com/node/39935&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://jordananastasiade.sys-con.com/node/39935</guid>
 <comments>http://jordananastasiade.sys-con.com/node/39935#feedback</comments>
</item>
<item>
 <title>Designing Objects for Concurrency in Java</title>
 <link>http://jordananastasiade.sys-con.com/node/35935</link>
 <description>Despite extensive development over many years and significant demonstrated benefits, the object-oriented paradigm remains poorly formalized. Several concurrent object-oriented languages have been designed and implemented based on the concurrent object model. However, upon attempting to apply formal techniques to a significant application, several well known shortcomings actually impeded progress dramatically right at the outset.&lt;p&gt;&lt;a href=&quot;http://jordananastasiade.sys-con.com/node/35935&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Sun, 01 Feb 1998 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://jordananastasiade.sys-con.com/node/35935</guid>
 <comments>http://jordananastasiade.sys-con.com/node/35935#feedback</comments>
</item>
<item>
 <title>Designing Objects for Concurrency</title>
 <link>http://jordananastasiade.sys-con.com/node/35806</link>
 <description>Java was designed to have all of the best features of existing languages. However, Java has no concept of asynchronous behavior. This is the main reason the threading mechanism is so important and that concurrent programming techniques are evolving quickly to the point where known patterns, whose behaviors are well understood, will become an integral part of the common Java environment.&lt;p&gt;&lt;a href=&quot;http://jordananastasiade.sys-con.com/node/35806&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Sun, 01 Jun 1997 00:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://jordananastasiade.sys-con.com/node/35806</guid>
 <comments>http://jordananastasiade.sys-con.com/node/35806#feedback</comments>
</item>
<item>
 <title>Designing Objects for Concurrency</title>
 <link>http://jordananastasiade.sys-con.com/node/35778</link>
 <description>Java&#039;s support for concurrency is sufficient enough to achieve a wide range of desired results. While the primitives provided are very powerful, they can also be easily misused and may lead to unpredictable behavior.  It is well known that in a multithreaded environment, due to the lack of mature tools available, the debugging process could easily modify the state of the program being debugged.&lt;p&gt;&lt;a href=&quot;http://jordananastasiade.sys-con.com/node/35778&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Tue, 01 Apr 1997 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://jordananastasiade.sys-con.com/node/35778</guid>
 <comments>http://jordananastasiade.sys-con.com/node/35778#feedback</comments>
</item>
</channel>
</rss>
