<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://www.dotnetzone.gr:443/cs/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Λοιπά θέματα</title><link>https://www.dotnetzone.gr:443/cs/forums/29/ShowForum.aspx</link><description>Οτιδήποτε άλλα θέματα developing που δεν κολλάνε σε κάποιο από τα υπόλοιπα forums!</description><dc:language>el</dc:language><generator>CommunityServer 2.1 SP3 (Build: 20423.1)</generator><item><title>Middleware Study</title><link>https://www.dotnetzone.gr:443/cs/forums/thread/315.aspx</link><pubDate>Tue, 19 Oct 2004 16:37:49 GMT</pubDate><guid isPermaLink="false">2622095e-976c-431a-859e-16783ec7ecd7:315</guid><dc:creator>Eyclides</dc:creator><slash:comments>0</slash:comments><comments>https://www.dotnetzone.gr:443/cs/forums/thread/315.aspx</comments><wfw:commentRss>https://www.dotnetzone.gr:443/cs/forums/commentrss.aspx?SectionID=29&amp;PostID=315</wfw:commentRss><description>&lt;p&gt;&lt;font style="BACKGROUND-COLOR: #efefef"&gt;Πρόσφατα η Middleware company εξέδωσε ένα νεό case study όπου συγκρίνεται το j2ee με το .NET. Τα κυριότερα σημεία του είναι ότι το .NET υπερέχει&amp;nbsp; σε &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;1. Performance&lt;br /&gt;2. Manageability&lt;br /&gt;3. Productivity&lt;br /&gt;4. TCO&lt;br /&gt;&lt;br /&gt;Μερικά αποσπάσματα από το report το οποίο μπορείτε να βρείτε στο &lt;a target="_blank" title="http://www.middlewareresearch.com/endeavors/040921IBMDOTNET/endeavor.jsp" href="http://www.middlewareresearch.com/endeavors/040921IBMDOTNET/endeavor.jsp"&gt;http://www.middlewareresearch.com/endeavors/040921IBMDOTNET/endeavor.jsp&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;font style="BACKGROUND-COLOR: #ffffff"&gt;“ In these tests the .NET implementation proved significantly more reliable in handling service interruptions than did the two J2EE implementations.&amp;nbsp; The WSAD implementation handled the controlled shutdown as well as the .NET implementation, and better than the RRD (which crashed when the downed server was restarted).&amp;nbsp;&amp;nbsp;&lt;br /&gt;&lt;br /&gt;&amp;nbsp;In the catastrophic failover test, however, only the .NET implementation recovered, while both J2EE implementations failed to do so.”&lt;/font&gt;&lt;/font&gt;&lt;/p&gt; &lt;p&gt;&lt;font style="BACKGROUND-COLOR: #efefef"&gt;&lt;font style="BACKGROUND-COLOR: #ffffff"&gt;Microsoft’s tight integration approach paid off in the development phase, where VS.NET and the .NET platform proved more productive than either RRD or WSAD with the WebSphere platform.”&amp;nbsp;&lt;/font&gt;&lt;/font&gt;&lt;/p&gt; &lt;p&gt;&lt;font style="BACKGROUND-COLOR: #efefef"&gt;&lt;font style="BACKGROUND-COLOR: #ffffff"&gt;“Most key elements of the .NET runtime infrastructure (basic application platform, Web server, load balancer, session server, message server) were already in place with the basic Windows Server 2003 installation….&lt;/font&gt;&lt;/font&gt;&lt;/p&gt; &lt;p&gt;&lt;font style="BACKGROUND-COLOR: #efefef"&gt;&lt;font style="BACKGROUND-COLOR: #ffffff"&gt;&amp;nbsp;The WebSphere team, by comparison, spent a great deal of time during the development phase installing the software and configuring it for basic functional tests.&amp;nbsp; They also spent considerable time overcoming fundamental configuration obstacles, such as patching the Linux kernel for Edge Server and configuring WebSphere for session replication.&amp;nbsp; The .NET team did not face such obstacles.”&lt;br /&gt;&amp;nbsp;&lt;/font&gt;&lt;/p&gt; &lt;div class="O" v=""&gt;&amp;nbsp;&lt;/div&gt;&lt;/font&gt;</description></item></channel></rss>