Generated.

[homepage.git] / blog / index.rss

diff --git a/blog/index.rss b/blog/index.rss
index d2d00b244d15657b028bbf116047db6214a630ca..7ef97cf9d2046d71e6780f519c3910906e911d6f 100644 (file)
--- a/blog/index.rss
+++ b/blog/index.rss
@@ -6,6 +6,40 @@
                 <link></link>
                 <atom:link href="index.rss" rel="self" type="application/rss+xml" />
        
                 <link></link>
                 <atom:link href="index.rss" rel="self" type="application/rss+xml" />
        

+       <item>
+               <title>Standardize on protocols and formats, not vendors and applications</title>
+               <link>Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
+               <guid isPermaLink="true">Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
+                <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
+               <description>
+&lt;p&gt;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.&lt;/p&gt;
+
+&lt;p&gt;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.&lt;/p&gt;
+
+&lt;p&gt;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.&lt;/p&gt;
+
+&lt;p&gt;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.&lt;/p&gt;
+</description>
+       </item>
+       

        <item>
                <title>Returning from Skolelinux developer gathering</title>
                <link>Returning_from_Skolelinux_developer_gathering.html</link>
        <item>
                <title>Returning from Skolelinux developer gathering</title>
                <link>Returning_from_Skolelinux_developer_gathering.html</link>


@@ -431,23 +465,5 @@ NUUG lykkes med å få ut sine opptak med like stor suksess.&lt;/p&gt;
 </description>
        </item>
        
 </description>
        </item>
        

-       <item>
-               <title>Lisensvalg for NUUG-opptakene endelig på plass</title>
-               <link>Lisensvalg_for_NUUG_opptakene_endelig_p___plass.html</link>
-               <guid isPermaLink="true">Lisensvalg_for_NUUG_opptakene_endelig_p___plass.html</guid>
-                <pubDate>Fri, 6 Mar 2009 21:20:00 +0100</pubDate>
-               <description>
-&lt;p&gt;Etter mange års meditasjon over temaet, har NUUG endelig klart å
-bestemme seg for hvilken lisens vi skal bruke på videoopptakene som
-gjøres av NUUGs videogruppe.  Ole Kristian har annonsert at lisensen
-blir &lt;a href=&quot;http://creativecommons.org/licenses/by-sa/3.0/no/&quot;&gt;Creative
-Commons Navngivelse-Del på samme vilkår 3.0 Norge&lt;/a&gt;.  Jeg er veldig
-glad for at denne saken endelig er landet.  Lisensen for opptaket til
-Stallman-foredraget ble en annen pga. at lisensvalget ikke var avklart
-på forhånd og IFI og PING ønsket CC-BY-ND, og må ses på som et unntak
-i denne sammenhengen.&lt;/p&gt;
-</description>
-       </item>
-       

         </channel>
 </rss>
         </channel>
 </rss>