From: Richard Bowen
Date: Wed, 16 Jan 2013 00:33:44 +0000 (+0000)
Subject: Provide an example in the introduction in order to motivate the lengthy
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=3573c2d88d031255e3331026584233d1b20f10b6;p=thirdparty%2Fapache%2Fhttpd.git
Provide an example in the introduction in order to motivate the lengthy
setup process.
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1433768 13f79535-47bb-0310-9956-ffa450edef68
---
diff --git a/docs/manual/howto/ssi.xml b/docs/manual/howto/ssi.xml
index 965c6384763..ea616fcd10f 100644
--- a/docs/manual/howto/ssi.xml
+++ b/docs/manual/howto/ssi.xml
@@ -66,14 +66,26 @@ existing HTML documents.
an existing HTML page, without having to serve the entire page
via a CGI program, or other dynamic technology.
+ For example, you might place a directive into an existing HTML
+ page, such as:
+
+
+
+
+
+ And, when the page is served, this fragment will be evaluated and replaced with its value:
+
+
+ Tuesday, 15-Jan-2013 19:28:54 EST
+
+
The decision of when to use SSI, and when to have your page
entirely generated by some program, is usually a matter of how
much of the page is static, and how much needs to be
recalculated every time the page is served. SSI is a great way
- to add small pieces of information, such as the current time.
- But if a majority of your page is being generated at the time
- that it is served, you need to look for some other
- solution.
+ to add small pieces of information, such as the current time - shown
+ above. But if a majority of your page is being generated at the time
+ that it is served, you need to look for some other solution.