From ead841c2f28d17e7916fba601e50763c8b01c122 Mon Sep 17 00:00:00 2001 From: Sol Jerome Date: Sat, 6 Mar 2010 20:39:12 +0000 Subject: doc: Integrate more unsorted documents Signed-off-by: Sol Jerome git-svn-id: https://svn.mcs.anl.gov/repos/bcfg/trunk/bcfg2@5754 ce84e21b-d406-0410-9b95-82705330c041 --- doc/unsorted/boundentry.txt | 15 --------------- 1 file changed, 15 deletions(-) delete mode 100644 doc/unsorted/boundentry.txt (limited to 'doc/unsorted/boundentry.txt') diff --git a/doc/unsorted/boundentry.txt b/doc/unsorted/boundentry.txt deleted file mode 100644 index 6dfa4b9bd..000000000 --- a/doc/unsorted/boundentry.txt +++ /dev/null @@ -1,15 +0,0 @@ -.. -*- mode: rst -*- - -.. _unsorted-boundentry: - -============= -Bound Entries -============= - -This feature is a mechanism to specify a full entry at once from a bundle. Traditionally, entries are defined in two stages. First, an abstract entry is defined in a bundle. This entry includes a type (the XML tag) and a name attribute. Then this entry is bound for a client, providing the appropriate instance of that entry for the client. Specifying a bound entry short-circuits this process; the only second stage processing on Bound entries is to remove the "Bound" prefix from the element tag. The use of a bound entry allows the single stage definition of a complete entry. Bound entries can be used for any type. - -.. code-block:: xml - - - - -- cgit v1.2.3-1-g7c22