April 2008 - tbnl-devel@common-lisp.net - mailman3.common-lisp.net

[hunchentoot-devel] Hunchentoot refactoring status report
by Hans Hübner 29 Apr '08

29 Apr '08

Hi, I have made a first round through Hunchentoot with the goals being: - Remove system specific code, relying on common compatibility libraries instead - Make single threaded operation a run-time option - Add timeout support for more platforms - Factor out SSL specific code so that conditional code is reduced - Remove mod_lisp support to ease refactoring and simplify the code I met most of these goals: - Instead of using functions from port-*.lisp, Hunchentoot now depends on bordeaux-threads for multiple thread support and on usocket for socket i/o. The GET-BACKTRACE function still remains as being non-portable. - Threading behavior is now controller by a CONNECTION-MANAGER. Every SERVER object has one CONNECTION-MANAGER and delegates listening and connection processing to that instance. Currently, there exist two CONNECTION-MANAGER classes: SINGLE-THREADED-CONNECTION-MANAGER listens and processes connections synchronously, ONE-THREAD-PER-CONNECTION-MANAGER listens in a separate thread and processes each connection in a new thread, as Hunchentoot did on multi-threaded platforms until now. The API for START-SERVER supports a THREADED keyword argument for simplicity, but it may be desirable to implement other CONNECTION-MANAGER classes in the future (for example to pool threads and/or separate connection management from request execution). Timeouts which are really an issue that is hard to solve, as there is no cross-implementation agreement on what timeouts are and how they should be implemented. As I need to make progress, I have added a platform specific SET-TIMEOUTS function which uses whatever mechanism the Lisp platform offers. I have removed the setting for separate read and write timeouts as I don't think that it is really useful make the distinction, but if someone has a really good use case, I may be adding them. I am currently testing my changes on more platforms and compilers. CCL and SBCL work fine, Lispworks is under investigation, I'll also look at CLISP later on. If there are other platforms that you'd like to see supported in the future, please check out the branch and send me patches. Branch SVN URL: http://common-lisp.net/project/tbnl/svn/branches/hans Trac URL for browsing: http://trac.common-lisp.net/tbnl/browser/branches/hans RSS URL for commits: http://trac.common-lisp.net/tbnl/timeline?changeset=on&max=50&daysback=90&f…

4 4

[hunchentoot-devel] How to capture the server instance
by Rommel Martinez 24 Apr '08

24 Apr '08

Is there a way to "capture" the server instance of Hunchentoot when I start the server like the following (yes I haven't bound it to a variable using say DEFVAR or DEFPARAMETER): CL-USER> (hunchentoot:start-server :port 9000) #<HUNCHENTOOT::SERVER {61917E79}> So that I can do something like the following when I want to stop the server: CL-USER> (hunchentoot:stop-server *foo*) -- Rommel M. Martinez <ebzzry(a)gmail.com>

3 2

[hunchentoot-devel] mod_lisp anyone?
by Hans Hübner 18 Apr '08

18 Apr '08

Hi, I'm planning to make some substantial changes to Hunchentoot and it would be helpful if I could remove mod_lisp support in this process. If you are using Hunchentoot with mod_lisp, please let us know. Thanks, Hans

13 36

[hunchentoot-devel] interning strings under Hunchentoot
by Andrei Stebakov 14 Apr '08

14 Apr '08

If I try to intern a string so I can call a function with this name, Hunchentoot returns an error that this function is not defined. For example, if in a HT request handler I call (apply 'some-func '("str1" "str2")) everything is OK, the function is called. If I call it like (apply (intern "SOME-FUNC") '("str1" "str2")) an exception occurs saying that SOME-FUNC is not defined. I need it to compose a function name by concatenating strings. BTW, when I do the same thing from REPL, both ways work. I am still just learing lisp and maybe this is not specifically HT related question, but I'd like to know why it happens. I am using hunchentoot-0.14.2 and sbcl 1.0.6. Thank you, Andrew

2 2

[hunchentoot-devel] Re: hunchentoot authorization
by Cyrus Harmon 13 Apr '08

13 Apr '08

I emailed Edi a week or so with some half-baked ideas about authorization/authentication and hunchentoot. He suggested continuing this discussion on the list, so I'm forwarding his initial comments below. For some background here, my initial approach to authorization with hunchentoot can be found at: http://git.cyrusharmon.org/cgi-bin/gitweb.cgi?p=hunchentoot-auth.git quoting my initial message, (some of) the motivation for this is to have: * HTML-based login, rather than the standard browser authentication dialog box * some notion of users/groups/realms * an easy way to serve content to: ** non-authenticated users ** authenticated but not necessarily authorized for this page users ** authenticated and authorized users Edi's questions and some answers are > 1. How do you enable users of hunchentoot-auth to use their own design > for the login and rejection pages? Yes, this is one of the main issues with the current design. Right now this is handled through the authorized-page macro. It allows for users (developers) to pass in a :login-page-function which should handle that. > 2. Where do you end up if the login was successful? Is it the same > page for all users? authorized-page is a macro that wraps each authorized page, so you end up on the selected page. not the most elegant way to do things. I'd like to remove the use of the macro here and tap into ht's dispatch machinery to do this more elegantly. > 3. Do you have a mechanism where, if I enter the URL of a page which > needs authorization, I first have to log in but will then be > redirected to the page I wanted to go to in the first place? yes, that's what the authorized-page macro does. again, there's probably a better approach. > This also raises the question how these are stored. Maybe provide > hooks or a backend API so that one can use an existing database and/or > combine with your own user class? (I.e. the USER class of > hunchentoot-auth should probably be prepared to be a mixin.) For ht-auth, this is stored in the realm class. It would certainly be simple enough to have a generic realm class along with a simple-realm or some such that has the current (admittedly trivial) functionality of storing the users/password-hashes in a local file. Further thoughts/comments on authorization and hunchentoot from the list? thanks, Cyrus On Apr 11, 2008, at 12:41 AM, Edi Weitz wrote: > Hi Cyrus, > > I've looked at this (a bit!) now and I'm adding my thoughts about the > issue below. Sorry for the delay. > > On Thu, 3 Apr 2008 11:52:32 -0700, Cyrus Harmon > <cyrus(a)cyrusharmon.org> wrote: > >> The issue is authentication. Hunchentoot kindly provides some basic >> services, but I'd like a more full-featured authentication mechanism >> with features like: >> >> * HTML-based login, rather than the standard browser authentication >> dialog box >> * some notion of users/groups/realms >> * an easy way to serve content to: >> ** non-authenticated users >> ** authenticated but not necessarily authorized for this page >> users >> ** authenticated and authorized users > > I agree that all of this is usually needed/wanted in a "modern" web > application and I've often implemented at least parts of this myself. > > Possible problems that I'm seeing here (if you want a flexible and > general solution): > > 1. How do you enable users of hunchentoot-auth to use their own design > for the login and rejection pages? > > 2. Where do you end up if the login was successful? Is it the same > page for all users? > > 3. Do you have a mechanism where, if I enter the URL of a page which > needs authorization, I first have to log in but will then be > redirected to the page I wanted to go to in the first place? > >> * an administrative UI for managing users/groups/realms > > This also raises the question how these are stored. Maybe provide > hooks or a backend API so that one can use an existing database and/or > combine with your own user class? (I.e. the USER class of > hunchentoot-auth should probably be prepared to be a mixin.) > >> * a UI for requesting new accounts, possibly with some sort of >> admin step hook or email based confirmation of accounts > > Yep. > > Would it make sense to continue this discussion on the mailing list? > > Cheers, > Edi.

5 8

[hunchentoot-devel] Sessions for realm aware Realm
by Andrea Chiumenti 12 Apr '08

12 Apr '08

Hello, I've created a small example of how the changes I've applied to hunchentoot manage session for realm awareness. To keep things clear I've only used cl-who, that nearly everyone knows here. The test comes with its usual asd file. To run the test, just run: CL-USER> (asdf:operate 'asdf:load-op :new-session) CL-USER> (new-session:start-test) and follow "http://localhost:4242/new-session/index.html" on your browser. Try it with cookies enabled and disabled, with *rewrite-for-session-urls* set to T and nil. Let me know, kiuma

2 5

Re: [hunchentoot-devel] Re: hunchentoot build error on ccl (with new version, via asdf)
by Raffaele 11 Apr '08

11 Apr '08

Hans, I am the same setup as yourself except I pulled CCL from the 1.1 branch as as per instructions. Upgrading is possible. How is stability compared to 1.1? Edi, Thanks! I'll RTFM better next time. Hunchentoot is excellent: it's been a real joy to build a RESTful server with it :) ----- Original Message ---- From: Hans Hübner <hans(a)huebner.org> To: General interest list for Hunchentoot and CL-WEBDAV <tbnl-devel(a)common-lisp.net> Sent: Friday, 11 April, 2008 6:50:34 PM Subject: Re: [hunchentoot-devel] Re: hunchentoot build error on ccl (with new version, via asdf) 2008/4/11, Edi Weitz <edi(a)agharta.de>: > On Fri, 11 Apr 2008 10:33:21 +0200, "Hans Hübner" <hans(a)huebner.org> wrote: > > > Correct. There has been a recent update to CL+SSL > > > But the error message was in Hunchentoot's port-mcl.lisp, not in > CL+SSL. That slipped my attention, sorry. The cure is the same, though: Upgrade CCL. -Hans > > _______________________________________________ > tbnl-devel site list > tbnl-devel(a)common-lisp.net > http://common-lisp.net/mailman/listinfo/tbnl-devel > _______________________________________________ tbnl-devel site list tbnl-devel(a)common-lisp.net http://common-lisp.net/mailman/listinfo/tbnl-devel Get the name you always wanted with the new y7mail email address. www.yahoo7.com.au/y7mail

2 1

Re: [hunchentoot-devel] Re: hunchentoot build error on ccl (with new version, via asdf)
by Raffaele 11 Apr '08

11 Apr '08

I have the same problem using the latest CCL 1.1-r8836S (DarwinPPC32) Read error between positions 4121 and 4465 in /usr/local/lisp/site/hunchentoot-0.15.6/port-mcl.lisp. > Error: Reader error: No external symbol named "STREAM-INPUT-TIMEOUT" in package #<Package "CCL"> . I had a look at port-mcl.lisp and it's expecting the symbol STREAM-INPUT-TIMEOUT in the CCL package. I'm assuming that this symbol is defined in release 1.2? Prior to the upgrade Hunchentoot 0.15.1 was working - except for below! The reason I decided to upgrade was because Hunchentoot would not return my formatted string as the response body after setf'ing return-code to +http-created+. If I did not set the return code (even to the default +http-ok+) Hunchentoot would return my string to the client. This was in response to a POST request. ----- Original Message ---- From: Hans Hübner <hans(a)huebner.org> To: General interest list for Hunchentoot and CL-WEBDAV <tbnl-devel(a)common-lisp.net> Sent: Friday, 11 April, 2008 2:00:11 AM Subject: Re: [hunchentoot-devel] Re: hunchentoot build error on ccl (with new version, via asdf) Current CL+SSL requires CCL from the Subversion trunk - Check out http://ccl.clozure.com/ccl-documentation.html for instructions on how to check out the trunk version of CCL from the repository. The 1.2 release is upcoming, but not yet done. -Hans _______________________________________________ tbnl-devel site list tbnl-devel(a)common-lisp.net http://common-lisp.net/mailman/listinfo/tbnl-devel Get the name you always wanted with the new y7mail email address. www.yahoo7.com.au/y7mail

3 4

[hunchentoot-devel] Re: hunchentoot build error on ccl (with new version, via asdf)
by Edi Weitz 10 Apr '08

10 Apr '08

On Thu, 10 Apr 2008 08:15:53 -0500, "Michael Kohout" <mwkohout(a)gmail.com> wrote: > I'm a bit of a noob, so no patchfile but I noticed this error when I > tried to build this morning: > > ? (asdf-install:install 'hunchentoot) > Install where? > 1) System-wide install: > System in /usr/local/asdf-install/site-systems/ > Files in /usr/local/asdf-install/site/ > 2) Personal installation: > System in /Users/development/.asdf-install-dir/systems/ > Files in /Users/development/.asdf-install-dir/site/ > 0) Abort installation. > --> 2 > ;;; ASDF-INSTALL: Downloading 129311 bytes from > http://weitz.de/files/hunchentoot.tar.gz to > /Users/development/asdf-install-0.asdf-install-tmp ... > ;;; ASDF-INSTALL: Installing HUNCHENTOOT in > /Users/development/.asdf-install-dir/site/, > /Users/development/.asdf-install-dir/systems/ > "ln -s > \"/Users/development/.asdf-install-dir/site/hunchentoot-0.15.6/hunchentoot-test.asd\" > \"/Users/development/.asdf-install-dir/systems/hunchentoot-test.asd\"" > ;;; ASDF-INSTALL: Found system definition: > /Users/development/.asdf-install-dir/site/hunchentoot-0.15.6/hunchentoot-test.asd > "ln -s > \"/Users/development/.asdf-install-dir/site/hunchentoot-0.15.6/hunchentoot.asd\" > \"/Users/development/.asdf-install-dir/systems/hunchentoot.asd\"" > ;;; ASDF-INSTALL: Found system definition: > /Users/development/.asdf-install-dir/site/hunchentoot-0.15.6/hunchentoot.asd > ;;; ASDF-INSTALL: Loading system ASDF-INSTALL::HUNCHENTOOT via ASDF. > ; loading system definition from > /Users/development/.asdf-install-dir/site/hunchentoot-0.15.6/hunchentoot.asd > into #<Package "ASDF0"> > ; registering #<SYSTEM :HUNCHENTOOT #x300041AAD8FD> as HUNCHENTOOT > ;;; ASDF-INSTALL: Downloading package URL-REWRITE, required by hunchentoot > > ;;; ASDF-INSTALL: Downloading 13123 bytes from > http://weitz.de/files/url-rewrite.tar.gz to > /Users/development/asdf-install-1.asdf-install-tmp ... > ;;; ASDF-INSTALL: Installing url-rewrite in > /Users/development/.asdf-install-dir/site/, > /Users/development/.asdf-install-dir/systems/ > "ln -s > \"/Users/development/.asdf-install-dir/site/url-rewrite-0.1.1/url-rewrite.asd\" > \"/Users/development/.asdf-install-dir/systems/url-rewrite.asd\"" > ;;; ASDF-INSTALL: Found system definition: > /Users/development/.asdf-install-dir/site/url-rewrite-0.1.1/url-rewrite.asd > "ln -s > \"/Users/development/.asdf-install-dir/site/url-rewrite-0.1.1/url-rewrite.system\" > \"/Users/development/.asdf-install-dir/systems/url-rewrite.system\"" > ;;; ASDF-INSTALL: Found system definition: > /Users/development/.asdf-install-dir/site/url-rewrite-0.1.1/url-rewrite.system > ;;; ASDF-INSTALL: Loading system ASDF-INSTALL::|url-rewrite| via ASDF. > ; loading system definition from > /Users/development/.asdf-install-dir/site/url-rewrite-0.1.1/url-rewrite.asd > into #<Package "ASDF0"> > ; registering #<SYSTEM :URL-REWRITE #x300041B0201D> as URL-REWRITE > ;;; ASDF-INSTALL: Loading system ASDF-INSTALL::HUNCHENTOOT via ASDF. > ;;; ASDF-INSTALL: Downloading package RFC2388, required by hunchentoot > > ;;; ASDF-INSTALL: Downloading 6177 bytes from > http://common-lisp.net/project/rfc2388/rfc2388_latest.tar.gz to > /Users/development/asdf-install-2.asdf-install-tmp ... > ;;; ASDF-INSTALL: Installing rfc2388 in > /Users/development/.asdf-install-dir/site/, > /Users/development/.asdf-install-dir/systems/ > "ln -s \"/Users/development/.asdf-install-dir/site/rfc2388/rfc2388.asd\" > \"/Users/development/.asdf-install-dir/systems/rfc2388.asd\"" > ;;; ASDF-INSTALL: Found system definition: > /Users/development/.asdf-install-dir/site/rfc2388/rfc2388.asd > ;;; ASDF-INSTALL: Loading system ASDF-INSTALL::|rfc2388| via ASDF. > ; loading system definition from > /Users/development/.asdf-install-dir/site/rfc2388/rfc2388.asd into #<Package > "ASDF0"> > ; registering #<SYSTEM :RFC2388 #x300041A7A43D> as RFC2388 > ;;; ASDF-INSTALL: Loading system ASDF-INSTALL::HUNCHENTOOT via ASDF. > ;;; ASDF-INSTALL: Downloading package MD5, required by hunchentoot > > ;;; ASDF-INSTALL: Downloading 9030 bytes from > http://files.b9.com/md5/md5-1.8.5.tar.gz to > /Users/development/asdf-install-3.asdf-install-tmp ... > ;;; ASDF-INSTALL: Installing md5 in > /Users/development/.asdf-install-dir/site/, > /Users/development/.asdf-install-dir/systems/ > "ln -s \"/Users/development/.asdf-install-dir/site/md5-1.8.5/md5.asd\" > \"/Users/development/.asdf-install-dir/systems/md5.asd\"" > ;;; ASDF-INSTALL: Found system definition: > /Users/development/.asdf-install-dir/site/md5-1.8.5/md5.asd > ;;; ASDF-INSTALL: Loading system ASDF-INSTALL::|md5| via ASDF. > ; loading system definition from > /Users/development/.asdf-install-dir/site/md5-1.8.5/md5.asd into #<Package > "ASDF0"> > ; registering #<SYSTEM MD5 #x300041B3DCBD> as MD5 > ;;; ASDF-INSTALL: Loading system ASDF-INSTALL::HUNCHENTOOT via ASDF. > ;;; ASDF-INSTALL: Downloading package CL-PPCRE, required by hunchentoot > > ;;; ASDF-INSTALL: Downloading 171687 bytes from > http://weitz.de/files/cl-ppcre.tar.gz to > /Users/development/asdf-install-4.asdf-install-tmp ... > ;;; ASDF-INSTALL: Installing cl-ppcre in > /Users/development/.asdf-install-dir/site/, > /Users/development/.asdf-install-dir/systems/ > "ln -s > \"/Users/development/.asdf-install-dir/site/cl-ppcre-1.3.2/cl-ppcre-test.asd\" > \"/Users/development/.asdf-install-dir/systems/cl-ppcre-test.asd\"" > ;;; ASDF-INSTALL: Found system definition: > /Users/development/.asdf-install-dir/site/cl-ppcre-1.3.2/cl-ppcre-test.asd > "ln -s > \"/Users/development/.asdf-install-dir/site/cl-ppcre-1.3.2/cl-ppcre.asd\" > \"/Users/development/.asdf-install-dir/systems/cl-ppcre.asd\"" > ;;; ASDF-INSTALL: Found system definition: > /Users/development/.asdf-install-dir/site/cl-ppcre-1.3.2/cl-ppcre.asd > "ln -s > \"/Users/development/.asdf-install-dir/site/cl-ppcre-1.3.2/cl-ppcre-test.system\" > \"/Users/development/.asdf-install-dir/systems/cl-ppcre-test.system\"" > ;;; ASDF-INSTALL: Found system definition: > /Users/development/.asdf-install-dir/site/cl-ppcre-1.3.2/cl-ppcre-test.system > "ln -s > \"/Users/development/.asdf-install-dir/site/cl-ppcre-1.3.2/cl-ppcre.system\" > \"/Users/development/.asdf-install-dir/systems/cl-ppcre.system\"" > ;;; ASDF-INSTALL: Found system definition: > /Users/development/.asdf-install-dir/site/cl-ppcre-1.3.2/cl-ppcre.system > ;;; ASDF-INSTALL: Loading system ASDF-INSTALL::|cl-ppcre| via ASDF. > ; loading system definition from > /Users/development/.asdf-install-dir/site/cl-ppcre-1.3.2/cl-ppcre.asd into > #<Package "ASDF0"> > ; registering #<SYSTEM :CL-PPCRE #x300041B1888D> as CL-PPCRE > ;;; ASDF-INSTALL: Loading system ASDF-INSTALL::HUNCHENTOOT via ASDF. > ;;; ASDF-INSTALL: Downloading package CL-FAD, required by hunchentoot > > ;;; ASDF-INSTALL: Downloading 11388 bytes from > http://weitz.de/files/cl-fad.tar.gz to > /Users/development/asdf-install-5.asdf-install-tmp ... > ;;; ASDF-INSTALL: Installing cl-fad in > /Users/development/.asdf-install-dir/site/, > /Users/development/.asdf-install-dir/systems/ > "ln -s \"/Users/development/.asdf-install-dir/site/cl-fad-0.6.2/cl-fad.asd\" > \"/Users/development/.asdf-install-dir/systems/cl-fad.asd\"" > ;;; ASDF-INSTALL: Found system definition: > /Users/development/.asdf-install-dir/site/cl-fad-0.6.2/cl-fad.asd > "ln -s > \"/Users/development/.asdf-install-dir/site/cl-fad-0.6.2/cl-fad.system\" > \"/Users/development/.asdf-install-dir/systems/cl-fad.system\"" > ;;; ASDF-INSTALL: Found system definition: > /Users/development/.asdf-install-dir/site/cl-fad-0.6.2/cl-fad.system > ;;; ASDF-INSTALL: Loading system ASDF-INSTALL::|cl-fad| via ASDF. > ; loading system definition from > /Users/development/.asdf-install-dir/site/cl-fad-0.6.2/cl-fad.asd into > #<Package "ASDF0"> > ; registering #<SYSTEM #:CL-FAD #x300041C75EDD> as CL-FAD > ;;; ASDF-INSTALL: Loading system ASDF-INSTALL::HUNCHENTOOT via ASDF. > ;;; ASDF-INSTALL: Downloading package CL-BASE64, required by hunchentoot > > ;;; ASDF-INSTALL: Downloading 6245 bytes from > http://files.b9.com/cl-base64/cl-base64-latest.tar.gz to > /Users/development/asdf-install-6.asdf-install-tmp ... > ;;; ASDF-INSTALL: Installing cl-base64 in > /Users/development/.asdf-install-dir/site/, > /Users/development/.asdf-install-dir/systems/ > "ln -s > \"/Users/development/.asdf-install-dir/site/cl-base64-3.3.2/cl-base64.asd\" > \"/Users/development/.asdf-install-dir/systems/cl-base64.asd\"" > ;;; ASDF-INSTALL: Found system definition: > /Users/development/.asdf-install-dir/site/cl-base64-3.3.2/cl-base64.asd > ;;; ASDF-INSTALL: Loading system ASDF-INSTALL::|cl-base64| via ASDF. > ; loading system definition from > /Users/development/.asdf-install-dir/site/cl-base64-3.3.2/cl-base64.asd into > #<Package "ASDF0"> > ; registering #<SYSTEM CL-BASE64 #x300041BC54BD> as CL-BASE64 > ; registering #<SYSTEM CL-BASE64-TESTS #x300041C2BF7D> as CL-BASE64-TESTS > ;;; ASDF-INSTALL: Loading system ASDF-INSTALL::HUNCHENTOOT via ASDF. > ;;; ASDF-INSTALL: Downloading package CHUNGA, required by hunchentoot > > ;;; ASDF-INSTALL: Downloading 16132 bytes from > http://weitz.de/files/chunga.tar.gz to > /Users/development/asdf-install-7.asdf-install-tmp ... > ;;; ASDF-INSTALL: Installing chunga in > /Users/development/.asdf-install-dir/site/, > /Users/development/.asdf-install-dir/systems/ > "ln -s \"/Users/development/.asdf-install-dir/site/chunga-0.4.1/chunga.asd\" > \"/Users/development/.asdf-install-dir/systems/chunga.asd\"" > ;;; ASDF-INSTALL: Found system definition: > /Users/development/.asdf-install-dir/site/chunga-0.4.1/chunga.asd > ;;; ASDF-INSTALL: Loading system ASDF-INSTALL::|chunga| via ASDF. > ; loading system definition from > /Users/development/.asdf-install-dir/site/chunga-0.4.1/chunga.asd into > #<Package "ASDF0"> > ; registering #<SYSTEM :CHUNGA #x300041D1515D> as CHUNGA > ;;; ASDF-INSTALL: Downloading package FLEXI-STREAMS, required by chunga > > ;;; ASDF-INSTALL: Downloading 123404 bytes from > http://weitz.de/files/flexi-streams.tar.gz to > /Users/development/asdf-install-8.asdf-install-tmp ... > ;;; ASDF-INSTALL: Installing flexi-streams in > /Users/development/.asdf-install-dir/site/, > /Users/development/.asdf-install-dir/systems/ > "ln -s > \"/Users/development/.asdf-install-dir/site/flexi-streams-0.14.0/flexi-streams.asd\" > \"/Users/development/.asdf-install-dir/systems/flexi-streams.asd\"" > ;;; ASDF-INSTALL: Found system definition: > /Users/development/.asdf-install-dir/site/flexi-streams-0.14.0/flexi-streams.asd > ;;; ASDF-INSTALL: Loading system ASDF-INSTALL::|flexi-streams| via ASDF. > ; loading system definition from > /Users/development/.asdf-install-dir/site/flexi-streams-0.14.0/flexi-streams.asd > into #<Package "ASDF0"> > ; registering #<SYSTEM :FLEXI-STREAMS #x300041C9FD0D> as FLEXI-STREAMS > ; registering #<SYSTEM :FLEXI-STREAMS-TEST #x300041C8A61D> as > FLEXI-STREAMS-TEST > ;;; ASDF-INSTALL: Downloading package TRIVIAL-GRAY-STREAMS, required by > flexi-streams > > ;;; ASDF-INSTALL: Downloading 3095 bytes from > http://common-lisp.net/project/cl-plus-ssl/download/trivial-gray-streams.ta… > /Users/development/asdf-install-9.asdf-install-tmp ... > ;;; ASDF-INSTALL: Installing trivial-gray-streams in > /Users/development/.asdf-install-dir/site/, > /Users/development/.asdf-install-dir/systems/ > "ln -s > \"/Users/development/.asdf-install-dir/site/trivial-gray-streams-2006-09-16/trivial-gray-streams.asd\" > \"/Users/development/.asdf-install-dir/systems/trivial-gray-streams.asd\"" > ;;; ASDF-INSTALL: Found system definition: > /Users/development/.asdf-install-dir/site/trivial-gray-streams-2006-09-16/trivial-gray-streams.asd > ;;; ASDF-INSTALL: Loading system ASDF-INSTALL::|trivial-gray-streams| via > ASDF. > ; loading system definition from > /Users/development/.asdf-install-dir/site/trivial-gray-streams-2006-09-16/trivial-gray-streams.asd > into #<Package "ASDF0"> > ; registering #<SYSTEM :TRIVIAL-GRAY-STREAMS #x300041CC382D> as > TRIVIAL-GRAY-STREAMS > ;;; ASDF-INSTALL: Loading system ASDF-INSTALL::|flexi-streams| via ASDF. > ;;; ASDF-INSTALL: Loading system ASDF-INSTALL::|chunga| via ASDF. > ;;; ASDF-INSTALL: Loading system ASDF-INSTALL::HUNCHENTOOT via ASDF. > Read error between positions 4121 and 4465 in > /Users/development/.asdf-install-dir/site/hunchentoot-0.15.6/port-mcl.lisp. >> Error: Reader error: No external symbol named "STREAM-INPUT-TIMEOUT" in > package #<Package "CCL"> . >> While executing: CCL::%PARSE-TOKEN, in process Listener(79). >> Type :POP to abort, :R for a list of available restarts. >> Type :? for other options. Thanks for the report. I'm forwarding this to the mailing list. Looks like it is related to Hans' recent changes. You'll probably have to update your CCL.

2 1

[hunchentoot-devel] Refactoring work plan
by Hans Hübner 10 Apr '08

10 Apr '08

I spent much of today looking at Hunchentoot and here is my plan for refactoring: Immediate high level goals: - Make threading optional on threaded platforms - Prepare for SERVE-EVENT based buffering - Clean up and refactor for better hackability In the longer term, I would like to make more of Hunchentoots data structures into classes that can be subclassed by applications. Requests, sessions and handlers come to mind, all of which currently exist, but they can't easily be extended in an object oriented fashion. Maybe it is good like that and an object oriented framework should be made optional. Also, there should be a logging API. Short term hacking plan: - Use USOCKET instead of private compatibility library. Currently, threading and socket I/O is intermixed because COMM:START-UP-SERVER from Lispworks is emulated by all platforms. Also, timeouts will be provided through USOCKET. - Use BORDEAUX-THREADS for threading. Currently, threads are assumed to be processes as in Lispworks. I particularily dislike the use of PROCESS-KILL to shutdown the server. - Clean up and refactor to reduce the number of special variables - Move platform specific code into subdirectory - Once we have decided whether we want to keep mod_lisp: Refactor so that mod_lisp specific code is isolated or remove it altogether. If you think anything of this is terrible and/or a bad idea, speak up. -Hans

4 4