Generated.

[homepage.git] / blog / archive / 2009 / 03 / index.html

diff --git a/blog/archive/2009/03/index.html b/blog/archive/2009/03/index.html
index 50f6d01d2978f6cb1c704ded39665335fb53e1fe..f2a427c80f2cfef65e4009dbca403619a8422132 100644 (file)
--- a/blog/archive/2009/03/index.html
+++ b/blog/archive/2009/03/index.html
@@ -643,6 +643,53 @@ now. :)</p>
 </div>
  <div class="padding"></div>
 
+<div class="entry">
+ <div class="title">
+ <a href="../../../Standardize_on_protocols_and_formats__not_vendors_and_applications.html">Standardize on protocols and formats, not vendors and applications</a>
+ </div>
+ <div class="date">
+  2009-03-30 11:50
+ </div>
+
+ <div class="body">
+  
+<p>Where I work at the University of Oslo, one decision stand out as a
+very good one to form a long lived computer infrastructure.  It is the
+simple one, lost by many in todays computer industry: Standardize on
+open network protocols and open exchange/storage formats, not applications.
+Applications come and go, while protocols and files tend to stay, and
+thus one want to make it easy to change application and vendor, while
+avoiding conversion costs and locking users to a specific platform or
+application.</p>
+
+<p>This approach make it possible to replace the client applications
+independently of the server applications.  One can even allow users to
+use several different applications as long as they handle the selected
+protocol and format.  In the normal case, only one client application
+is recommended and users only get help if they choose to use this
+application, but those that want to deviate from the easy path are not
+blocked from doing so.</p>
+
+<p>It also allow us to replace the server side without forcing the
+users to replace their applications, and thus allow us to select the
+best server implementation at any moment, when scale and resouce
+requirements change.</p>
+
+<p>I strongly recommend standardizing - on open network protocols and
+open formats, but I would never recommend standardizing on a single
+application that do not use open network protocol or open formats.</p>
+
+ </div>
+ <div class="tags">
+ 
+
+ 
+  Tags: <a href="../../../tags/debian">debian</a>, <a href="../../../tags/english">english</a>, <a href="../../../tags/nuug">nuug</a>, <a href="../../../tags/standard">standard</a>.
+ 
+ </div>
+</div>
+ <div class="padding"></div>
+
  <p style="text-align: right;"><a href="03.rss"><img src="../../../xml.gif" alt="RSS Feed" width="36" height="14"></a></p>
 
 
@@ -659,7 +706,7 @@ now. :)</p>
 
 <li><a href="../../../archive/2009/02/">February (8)</a></li>
 
-<li><a href="../../../archive/2009/03/">March (11)</a></li>
+<li><a href="../../../archive/2009/03/">March (12)</a></li>
 
 </ul></li>
 
@@ -685,11 +732,11 @@ now. :)</p>
 
  <li><a href="../../../tags/aros">aros (1)</a></li>
 
- <li><a href="../../../tags/debian">debian (5)</a></li>
+ <li><a href="../../../tags/debian">debian (6)</a></li>
 
  <li><a href="../../../tags/debian edu">debian edu (6)</a></li>
 
- <li><a href="../../../tags/english">english (8)</a></li>
+ <li><a href="../../../tags/english">english (9)</a></li>
 
  <li><a href="../../../tags/fiksgatami">fiksgatami (1)</a></li>
 
@@ -699,7 +746,7 @@ now. :)</p>
 
  <li><a href="../../../tags/norsk">norsk (31)</a></li>
 
- <li><a href="../../../tags/nuug">nuug (29)</a></li>
+ <li><a href="../../../tags/nuug">nuug (30)</a></li>
 
  <li><a href="../../../tags/personvern">personvern (3)</a></li>
 
@@ -707,7 +754,7 @@ now. :)</p>
 
  <li><a href="../../../tags/rss">rss (1)</a></li>
 
- <li><a href="../../../tags/standard">standard (1)</a></li>
+ <li><a href="../../../tags/standard">standard (2)</a></li>
 
  <li><a href="../../../tags/stavekontroll">stavekontroll (1)</a></li>