[version 0.8.1
ediware**20070404170018] {
hunk ./CHANGELOG 1
+Version 0.8.1
+2007-04-04
+Added HUNCHENTOOT-MP package (suggested by Cyrus Harmon)
+Only invoke MARK-AND-SWEEP for 32-bit versions of LW (thanks to Chris Dean)
+Exported REASON-PHRASE
+
hunk ./doc/index.html 111
+  <li><a href="#ht-mp">The HUNCHENTOOT-MP package</a>
+  <li><a href="#performance">Performance</a>
hunk ./doc/index.html 131
-      <li>and my own <a href='http://weitz.de/chunga/'>Chunga</a>, <a href='http://weitz.de/cl-ppcre/'>CL-PPCRE</a>, and <a href='http://weitz.de/url-rewrite/'>URL-REWRITE</a> (plus <a href="http://weitz.de/cl-who/">CL-WHO</a> for the <a href="#example">example code</a>). 
+      <li>and my own <a href='http://weitz.de/flexi-streams/'>FLEXI-STREAMS</a>, <a href='http://weitz.de/chunga/'>Chunga</a>, <a href='http://weitz.de/cl-ppcre/'>CL-PPCRE</a>, and <a href='http://weitz.de/url-rewrite/'>URL-REWRITE</a> (plus <a href="http://weitz.de/cl-who/">CL-WHO</a> for the <a href="#example">example code</a>). 
hunk ./doc/index.html 141
-current version is 0.8.0.  There's also a port
+current version is 0.8.1.  There's also a port
hunk ./doc/index.html 2108
+<p><br>[Function]
+<br><a class=none name="reason-phrase"><b>reason-phrase</b> <i>return-code</i> =&gt; <i>string</i></a>
+
+<blockquote><br> Returns a reason phrase for the HTTP return
+code <code><i>return-code</i></code> (which should be an integer)
+or <code>NIL</code> for return codes Hunchentoot doesn't know.
+</blockquote>
+
+<br>&nbsp;<br><h3><a class=none name="ht-mp">The HUNCHENTOOT-MP package</a></h3>
+
+Hunchentoot creates an
+additional <a
+href="http://www.lispworks.com/documentation/HyperSpec/Body/11_.htm">package</a> <code>HUNCHENTOOT-MP</code>
+which exports a couple of MP-related symbols
+(namely <code>MAKE-LOCK</code>, <code>WITH-LOCK</code>, <code>PROCESS-RUN-FUNCTION</code>,
+and <code>PROCESS-KILL</code>).  These functions and macros have to be
+in Hunchentoot's small portability shim anyway and even if you don't
+spawn your own threads there might be occasions where you want to at
+least use the lock-related functionality to write thread-safe portable
+code.  See the corresponding documentation strings and/or the source
+code for more information.
+
+<br>&nbsp;<br><h3><a class=none name="performance">Performance</a></h3>
+
+If you're concerned about Hunchentoot's performance, you should first
+and foremost check if you aren't wasting your time with premature
+optimization.  Make a reasonable estimate of the amount of traffic
+your website should be able to handle and don't try to benchmark for
+loads Google would be proud of.  Here's a part of an interview with
+someone called John Witchel about his experiences with his
+company <em>Red Gorilla</em> that can't be quoted often enough (it
+seems the original source of the interview has vanished):
+
+<blockquote>
+<b>Q:</b> If you could go back and change anything, would <em>Red Gorilla</em> still be
+in business today?
+<p>
+<b>A:</b> Yes. I would start small and grow as the demand grew. That's what I'm
+doing now.
+<p>
+Back then we planned to be huge from the outset. So we built this
+monster platform on BEA, Sun and Oracle. We had huge dedicated
+connectivity pipes. We had two full racks clustered and fully
+redundant. We had E450's with RAID-5 and all 4 CPU slots filled,
+E250s, F5 load balancers... the cost of keeping that system on was
+enormous. The headcount to keep it humming was enormous too.
+<p>
+The truth is, we could have run the whole company on my laptop using a
+cable modem connection.
+</blockquote>
+
+Having said that, my experience is that Hunchentoot doesn't have to
+hide behind Apache when it comes to
+serving <a href="#handle-static-file">static files</a>.  If
+you <em>really</em> have performance problems with Hunchentoot, there
+are two things I'm aware of you should watch out for.
+<ul>
+<li>Check how your Lisp implementation implements multi-processing.
+While I write this (April 2007), some Lisps, like CMUCL, still use
+their
+own <a
+href="http://en.wikipedia.org/wiki/Multithreading"><em>green</em>
+threads</a>, and some others, like AllegroCL and LispWorks, use
+OS-threads but allow only one Lisp thread at a time.  Unless you're
+using a Lisp that employs "real" symmetric multi-processing like SBCL
+(on some platforms) or OpenMCL, you shouldn't compare apples with
+oranges.  (Note: For CMUCL, you also shouldn't forget to use the
+dreaded <a
+href="http://wiki.alu.org/Lisp_Gotchas"><code>MP::STARTUP-IDLE-AND-TOP-LEVEL-LOOPS</code></a>.)
+<li>All text output sent from <a href="#handlers">handlers</a> goes
+through two layers
+of <a
+href="http://www.nhplace.com/kent/CL/Issues/stream-definition-by-user.html">Gray
+streams</a> by default
+(<a href="http://weitz.de/flexi-streams/">FLEXI-STREAMS</a>
+and <a href="http://weitz.de/chunga/">Chunga</a>).  This isn't an
+issue for small to medium-sized pages, but can be for large ones.
+There are several ways to cope with this
+- <a
+href="http://common-lisp.net/pipermail/tbnl-devel/2007-March/001093.html">return
+binary data from
+handlers</a>, <a
+href="http://common-lisp.net/pipermail/tbnl-devel/2007-March/001099.html">bypass
+FLEXI-STREAMS</a>, sit behind <a href="#mod_lisp">mod_lisp</a>, etc.
+Try it, and if you <em>really</em> think that Hunchentoot is too slow
+for what you're trying to do and what you'll need, ask on
+the <a href="#href">mailing list</a> and we'll try to help.
+</ul>
+
hunk ./doc/index.html 2376
+      <li><a href="#reason-phrase"><code>reason-phrase</code></a>
hunk ./doc/index.html 2452
-$Header: /usr/local/cvsrep/hunchentoot/doc/index.html,v 1.74 2007/03/30 23:59:29 edi Exp $
+$Header: /usr/local/cvsrep/hunchentoot/doc/index.html,v 1.76 2007/04/04 07:52:09 edi Exp $
hunk ./headers.lisp 2
-;;; $Header: /usr/local/cvsrep/hunchentoot/headers.lisp,v 1.16 2007/03/30 22:08:48 edi Exp $
+;;; $Header: /usr/local/cvsrep/hunchentoot/headers.lisp,v 1.17 2007/04/02 21:21:06 edi Exp $
hunk ./headers.lisp 92
-         (status-line (status-line return-code))
+         (reason-phrase (reason-phrase return-code))
hunk ./headers.lisp 125
-    (unless status-line
+    (unless reason-phrase
hunk ./headers.lisp 130
-            status-line (status-line return-code)))
+            reason-phrase (reason-phrase return-code)))
hunk ./headers.lisp 147
-                (format nil "<html><head><title>~D ~A</title></head><body><h1>~A</h1>~A<p><hr>~A</p></body></html>"
-                        return-code status-line status-line
+                (format nil "<html><head><title>~D ~A</title></head><body><h1>~:*~A</h1>~A<p><hr>~A</p></body></html>"
+                        return-code reason-phrase
hunk ./headers.lisp 168
-           (write-header-line t "Status" (format nil "~D ~A" return-code status-line)))
+           (write-header-line t "Status" (format nil "~D ~A" return-code reason-phrase)))
hunk ./headers.lisp 171
-                  (format nil "HTTP/1.1 ~D ~A" return-code status-line)))
+                  (format nil "HTTP/1.1 ~D ~A" return-code reason-phrase)))
hunk ./headers.lisp 304
-                                  (status-line +http-continue+))))
+                                  (reason-phrase +http-continue+))))
hunk ./hunchentoot.asd 2
-;;; $Header: /usr/local/cvsrep/hunchentoot/hunchentoot.asd,v 1.28 2007/03/30 23:59:28 edi Exp $
+;;; $Header: /usr/local/cvsrep/hunchentoot/hunchentoot.asd,v 1.29 2007/04/04 07:52:06 edi Exp $
hunk ./hunchentoot.asd 37
-(defvar *hunchentoot-version* "0.8.0"
+(defvar *hunchentoot-version* "0.8.1"
hunk ./packages.lisp 2
-;;; $Header: /usr/local/cvsrep/hunchentoot/packages.lisp,v 1.24 2007/03/30 22:08:48 edi Exp $
+;;; $Header: /usr/local/cvsrep/hunchentoot/packages.lisp,v 1.25 2007/04/04 07:52:06 edi Exp $
hunk ./packages.lisp 32
+(defpackage :hunchentoot-mp
+  (:nicknames :tbnl-mp)
+  (:export :make-lock
+           :with-lock
+           :process-run-function
+           :process-kill))
+
hunk ./packages.lisp 41
-  (:use :cl :cl-ppcre :chunga :flexi-streams :url-rewrite)
+  (:use :cl :cl-ppcre :chunga :flexi-streams :url-rewrite :hunchentoot-mp)
hunk ./packages.lisp 219
+
+
hunk ./port-sbcl.lisp 2
-;;; $Header: /usr/local/cvsrep/hunchentoot/port-sbcl.lisp,v 1.10 2007/03/09 10:50:24 edi Exp $
+;;; $Header: /usr/local/cvsrep/hunchentoot/port-sbcl.lisp,v 1.11 2007/04/04 07:52:06 edi Exp $
hunk ./port-sbcl.lisp 71
+  (declare (ignorable name))
hunk ./test/test.lisp 2
-;;; $Header: /usr/local/cvsrep/hunchentoot/test/test.lisp,v 1.17 2007/03/09 12:20:57 edi Exp $
+;;; $Header: /usr/local/cvsrep/hunchentoot/test/test.lisp,v 1.18 2007/04/02 21:21:19 edi Exp $
hunk ./test/test.lisp 56
-  (let ((=value= (gensym)))
+  (let ((=value= (gensym))
+        (=first= (gensym)))
hunk ./test/test.lisp 72
-                                             for first = t then nil
-                                             unless first
+                                             for ,=first= = t then nil
+                                             unless ,=first=
hunk ./util.lisp 2
-;;; $Header: /usr/local/cvsrep/hunchentoot/util.lisp,v 1.24 2007/03/30 08:16:06 edi Exp $
+;;; $Header: /usr/local/cvsrep/hunchentoot/util.lisp,v 1.26 2007/04/04 07:52:06 edi Exp $
hunk ./util.lisp 153
-(defun status-line (return-code)
-  "Returns a meaningful status line for the http return code
-RETURN-CODE \(which should be an integer) or NIL for uncommon return
-codes."
+(defun reason-phrase (return-code)
+  "Returns a reason phrase for the HTTP return code RETURN-CODE
+\(which should be an integer) or NIL for return codes Hunchentoot
+doesn't know."
hunk ./util.lisp 464
-  "The default for *CLEANUP-FUNCTION*.  Invokes a GC on LispWorks and
-does nothing on other Lisps."
-  #+:lispworks
+  "The default for *CLEANUP-FUNCTION*.  Invokes a GC on 32-bit
+LispWorks and does nothing on other Lisps."
+  #+(and :lispworks (not :lispworks-64bit))
hunk ./util.lisp 468
+
}