<?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>The [intranet] web client is dead!</title><link>https://www.dotnetzone.gr:443/cs/blogs/fault/archive/2007/03/19/the-intranet-web-client-is-dead.aspx</link><description>Admittedly, I'm exaggerating a little (I am just trying to provoke Panos). But I am tired of hearing people, especially in enterprise scenarios, say "I want to use a web client for this, and a web client for that" without really thinking about it, or</description><dc:language>el</dc:language><generator>CommunityServer 2.1 SP3 (Build: 20423.1)</generator><item><title>re: The [intranet] web client is dead!</title><link>https://www.dotnetzone.gr:443/cs/blogs/fault/archive/2007/03/19/the-intranet-web-client-is-dead.aspx#26748</link><pubDate>Tue, 20 Mar 2007 21:53:15 GMT</pubDate><guid isPermaLink="false">2622095e-976c-431a-859e-16783ec7ecd7:26748</guid><dc:creator>cap</dc:creator><description>&lt;p&gt;Indeed, this is a very interesting (and true) point of view. But there's one more argument that you are not discussing in this post: OS independence. Web applications usually run in systems which use a popular browser, regardless of whether the operating system is Windows, &amp;nbsp;Linux, or anything else. &lt;/p&gt;
&lt;p&gt;Of course, this is not true in all cases, since some Web apps are configured and optimized for a specific browser (IE, for example) which is found primarily on Windows :) But the argument itself is a strong marketing tool for those who sell or create Web applications.&lt;/p&gt;
&lt;p&gt;On the other hand, in Intranet / Extranet scenarios, OS independence makes sense in a limited number of cases. So, I would agree that the Smart Client approach is an alternative that could prove more usable, cost-effective, and user-friendly. Its main advantage, though, IMHO, is that it can provide a familiar user interface and not a custom one as is the case with most web applications out there.&lt;/p&gt;</description></item><item><title>re: The [intranet] web client is dead!</title><link>https://www.dotnetzone.gr:443/cs/blogs/fault/archive/2007/03/19/the-intranet-web-client-is-dead.aspx#26785</link><pubDate>Wed, 21 Mar 2007 03:54:07 GMT</pubDate><guid isPermaLink="false">2622095e-976c-431a-859e-16783ec7ecd7:26785</guid><dc:creator>Dimitris Papadimitriou</dc:creator><description>&lt;p&gt;I'm not sure if Intranet web client is dead yet, but let's hope and do our best to kill it as soon as possible! :)&lt;/p&gt;
&lt;p&gt;My thoughts exactly!&lt;/p&gt;
&lt;p&gt;Currently I'm working on a client/server system that is ClickOnce deployed and it seems to be going great both in technical viewpoint and user acceptance. And since after deployment client communicates with server using web services the system works smoothly both in intranet and internet environment.&lt;/p&gt;</description></item></channel></rss>