svn commit: rev 22095 - in avalon/trunk/central/site/src/xdocs/central/laboratory/castle: . dynamicproxy managedextensions microkernel

Author: hammett
Date: Thu Jun 24 20:27:07 2004
New Revision: 22095

Added:
   avalon/trunk/central/site/src/xdocs/central/laboratory/castle/
   avalon/trunk/central/site/src/xdocs/central/laboratory/castle/dynamicproxy/
   avalon/trunk/central/site/src/xdocs/central/laboratory/castle/index.xml   (contents, props changed)
   avalon/trunk/central/site/src/xdocs/central/laboratory/castle/managedextensions/
   avalon/trunk/central/site/src/xdocs/central/laboratory/castle/microkernel/
Log:
Initial documents

Added: avalon/trunk/central/site/src/xdocs/central/laboratory/castle/index.xml
==============================================================================
--- (empty file)
+++ avalon/trunk/central/site/src/xdocs/central/laboratory/castle/index.xml	Thu Jun 24 20:27:07 2004
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<article>
+  <title>Avalon Castle Container</title>
+
+  <section>
+    <title>A container for CLI</title>
+
+    <para>Avalon Castle is the last one of a few attempts to deliver a
+    container for the CLI (.Net and Mono) world. Although it can be viewed as
+    a port of Avalon, it benefits from several features offered by the
+    CLR.</para>
+
+    <para>Other important difference of Castle container is its simplicity.
+    Based on Microkernel pattern, the user can easily modified, extend or
+    adapt it to match his requirements. No hard contracts, no obligations.
+    Just good and old Inversion of Control and stills Avalon.</para>
+  </section>
+
+  <section>
+    <title>Primary differences</title>
+
+    <para>The first difference to be noticed relates to the no obligation of
+    using Avalon interfaces or attributes at all. </para>
+  </section>
+</article>
\ No newline at end of file