1. added a 'browse-through' navigation

2. improved performance by passing -flush to FastCgiExternalServer
3. emphasized links in text

1 files changed, 2 insertions, 0 deletions

diff --git a/htdocs/exceptions/runtime.chtml b/htdocs/exceptions/runtime.chtml
index d0a8e14..9a72afd 100644
--- a/htdocs/exceptions/runtime.chtml
+++ b/htdocs/exceptions/runtime.chtml
@@ -1,28 +1,30 @@
 % html(); return; /* vim:set ft=sitecing: */
 %%derive layout = "/ancestry/layout.chtml";
 <%constructor>
  b_strict = false;
+ PN_PREV("/exceptions/compile","compile-time","compile-time errors");
+ PN_NEXT("/sources","sources","source browser");
 </%constructor>
 <%codemethod string title() %>
  return "runtime exceptions handling";
 </%codemethod>
 <%method void content() %>
  <h1>site-C-ing runtime exception handling</h1>
  <p>
   The component may throw an exception while executing and the
   <em>site-C-ing</em> will gladly pass it to the handler component which will
   give the user appropriate output (unless it throws an exception itself, of
   course). Here you will see an example output provided by the handler bundled
   with the <em>site-C-ing</em>.
  </p>
 
  <p>
   Suppose you have <a href="/view/htdocs/exceptions/development/runtime.chtml"
   target="insert" title="the link opens in the frame below">a component</a>,
   which at some point throws an exception. Of course, <em>site-C-ing</em> will
   catch the exception and pass it to <a
   href="/view/htdocs/handlers/exception_dev" target="insert" title="the link
   opens in the frame below">the handler</a>, specified in <a
   href="/view/htdocs/exceptions/development/.scrc" target="insert" title="the
   link opens in the frame below">the configuration file</a>, which will produce
   some nice, human-readable <a href="/exceptions/development/runtime"