October 2006 - tbnl-devel@common-lisp.net

[hunchentoot-devel] New Hunchentoot version 0.4.0 (aka "good-bye TBNL")
by Edi Weitz 10 Oct '06

10 Oct '06

OK, as far as I am concerned, TBNL is hereby deprecated. If someone else wants to inherit and maintain it, they should contact me. I think that the current release of Hunchentoot (modulo errors) is a worthy successor/replacement for all implementations supported by TBNL. In particular, I expect less issues with SBCL due to the use of FLEXI-STREAMS. Please download, install, play with it, and report problems to the list: http://weitz.de/files/hunchentoot.tar.gz Note that some parts of the API have been slightly changed. Consult the docs if in doubt. And if you find mistakes in the documentation, please report them as well. Have fun, Edi.

2 2

[tbnl-devel] TBNL and SBCL
by David J. Neu 09 Oct '06

09 Oct '06

Hi, I know that there has been a lot of discussion about how nicely TBNL and SBCL play together, and as someone new to this list I wanted to ask a few question about the current situation. The architecture, I envision has Apache sitting "in-front", passing requests back to TBNL. In view of http://common-lisp.net/pipermail/tbnl-devel/2006-October/000710.html and http://common-lisp.net/pipermail/tbnl-devel/2006-October/000711.html do I understand correctly, that the new road ahead is that TBNL is sort of being "merged" with Hunchentoot to create an enhanced TBNL, that is less dependent on "other" packages and that this new release will reduce the issues related to TBNL/SBCL compatibility? Many thanks! Cheers, David

2 1

[tbnl-devel] Hunchentoot beta no. 4
by Edi Weitz 09 Oct '06

09 Oct '06

http://weitz.de/files/hunchentoot-beta.tar.gz Use at your own risk, as usual. FYI, I'm currently re-factoring the code (and changing parts of the API while I'm at it). I do this with LispWorks on Windows 99% of the time, so I'm not even sure if the code still compiles on SBCL or other Lisps. I'm happy if you send me notes about problems you're encountering. And, sorry, the documentation still hasn't been updated. Cheers, Edi.

3 6

[tbnl-devel] SBCL, hunchentoot, performance
by Graham Fawcett 06 Oct '06

06 Oct '06

Hi again folks, Maybe it's a bit early to be asking about hunchentoot, sbcl and performance... but heck, let me ask anyway. :-) Trying the hunchentoot beta on SBCL 0.9.17, I ran tbnl-test, and uploaded a ~0.75MB binary file. (Which worked!) Testing with 'ab', I downloaded the file -- but I wasn't able to get a download faster than 359KB/sec, or 2 seconds per download, on a fast network. I also observed >95% CPU activity during the download (about 50/50 between user and system). Profiling the :TBNL package, and downloading the file again, showed this: seconds | consed | calls | sec/call | name -------------------------------------------------------- 1.740 | 35,748,752 | 1 | 1.739901 | HANDLE-STATIC-FILE 0.004 | 8,184 | 1 | 0.003998 | TBNL::READ-HTTP-HEADERS 0.004 | 24,912 | 6 | 0.000665 | TBNL::WRITE-HEADER-LINE/HTTP and profiling :FLEX instead, then repeating the download, showed: seconds | consed | calls | sec/call | name ------------------------------------------------------------- 0.009 | 81,920 | 352 | 0.000027 | FLEXI-STREAMS::READ-BYTE* 0.000 | 106,051,824 | 1,488,124 | 0.000000 | FLEXI-STREAMS::WRITE-BYTE* The consing numbers seem pretty high. :-) I'm not sure how to interpret the 0.0 seconds for the write-byte* calls -- a hundred million conses might be fast, but not instantaneous! It's notable that the reported "profiling overhead" was ~15 seconds, perhaps it was just a profiling error. (I'm not a SLIME-profiling expert -- advice is welcome.) Is this degree of performance similar to what you see under Lispworks? I'm not throwing stones at beta code, just trying to interpret what I'm seeing here. Thanks, Graham

2 8

Re: [tbnl-devel] TBNL survey / re-org
by Edi Weitz 06 Oct '06

06 Oct '06

On Fri, 29 Sep 2006 18:16:26 -0400, Travis Cross <travis(a)officetone.com> wrote: > After you released Hunchentoot, I took a hard look at the source and > have been considering factoring out the non-portable code ever > since. I'd be terribly happy if you beat me to it though ;) There's a slight chance that this will happen... :) > Another project on my TBNL agenda that I started part way down was > seeing if I could remove some dependencies (primarily kmrcl) without > adding a whole lot a code to TBNL. LispWorks/Hunchentoot doesn't use KMRCL, so that's the plan for SBCL and the other Lisps as well. > Do you happen to be sold on the wonders of the Darcs version control > system? ;) If you're not strongly tied to whatever VCS you're > currently using, a public darcs repository could be a real boon. You wouldn't win anything, because I immediately make a new release if I add new code. Im the case of RDNZL I once tried with a public repository, but although several people had write access nothing came out of it. The only result was that it became harder for me and I couldn't work offline anymore... Cheers, Edi.

4 20

[tbnl-devel] tbnl, sbcl and binary uploads: still a problem?
by Graham Fawcett 04 Oct '06

04 Oct '06

Hi folks, Is anyone still encountering problems with binary uploads using TBNL with SBCL and the mod_lisp front-end? I've applied Travis Cross' patches to KMRCL and RFC2388. But in spite of the patches, I'm seeing errors when trying to upload a binary file to the tbnl-test demo application. For example: #<SB-SYS:FD-STREAM for "a constant string" {B7C2F69}> (:EXTERNAL-FORMAT :UTF-8): the octet sequence (226 227 207) cannot be decoded. I'm using SBCL 0.9.15 on Linux 2.6; TBNL 0.11.3, KMRCL-1.89, and a fresh RFC2388, with the Cross patches applied. *features* and SLIME backtrace are below. I'm happy to do more testing/debugging, but perhaps someone could help point me in the right direction. Thanks, Graham *features* (:CL-WHO :TBNL :TBNL-SBCL-DEBUG-PRINT-VARIABLE-ALIST :TBNL-BIVALENT-STREAMS :URL-REWRITE :KMR-NORMAL-DSDC :KMR-NORMAL-CESD :CL-PPCRE :KMR-MOP :ASDF :SB-THREAD :ANSI-CL :COMMON-LISP :SBCL :UNIX :SB-DOC :SB-TEST :SB-LDB :SB-PACKAGE-LOCKS :SB-UNICODE :SB-SOURCE-LOCATIONS :IEEE-FLOATING-POINT :X86 :ELF :LINUX :GENCGC :STACK-GROWS-DOWNWARD-NOT-UPWARD :C-STACK-IS-CONTROL-STACK :STACK-ALLOCATABLE-CLOSURES :ALIEN-CALLBACKS :LINKAGE-TABLE :OS-PROVIDES-DLOPEN :OS-PROVIDES-DLADDR :OS-PROVIDES-PUTWC) Snipped backtrace: 7: (TBNL::MAYBE-INVOKE-DEBUGGER #<SB-INT:STREAM-DECODING-ERROR {CFC3BC1}>) 8: (SIGNAL #<SB-INT:STREAM-DECODING-ERROR {CFC3BC1}>) 9: (ERROR SB-INT:STREAM-DECODING-ERROR) 10: (SB-INT:STREAM-DECODING-ERROR #<SB-SYS:FD-STREAM for "a constant string" {C6F56C1}> (226 227 207)) 11: (SB-IMPL::STREAM-DECODING-ERROR-AND-HANDLE #<SB-SYS:FD-STREAM for "a constant string" {C6F56C1}> 3) 12: (SB-IMPL::INPUT-CHAR/UTF-8 #<SB-SYS:FD-STREAM for "a constant string" {C6F56C1}> NIL NIL) 13: (READ-CHAR #<SB-SYS:FD-STREAM for "a constant string" {C6F56C1}> NIL NIL #<unused argument>) 14: ((FLET RFC2388::RUN) #<SB-SYS:FD-STREAM for "file /tmp/tbnl/tbnl-16" {CFC39B1}>) 15: (RFC2388::READ-UNTIL-NEXT-BOUNDARY #<SB-SYS:FD-STREAM for "a constant string" {C6F56C1}> "--------------------$ 16: ((SB-PCL::FAST-METHOD RFC2388:PARSE-MIME (STREAM T)) #<unavailable argument> #<unavailable argument> #<SB-SYS:$ 17: (TBNL::PARSE-RFC2388-FORM-DATA #<SB-SYS:FD-STREAM for "a constant string" {C6F56C1}> "multipart/form-data; bou$ 18: ((SB-PCL::FAST-METHOD INITIALIZE-INSTANCE :AFTER (TBNL::REQUEST)) (#(NIL 1 2 0 3 5 8 4 6) . #()) #<unavailable$ 19: ((LAMBDA (SB-PCL::|.P0.|)) #<unavailable argument>) 20: (TBNL::PROCESS-REQUEST (("content-stream" . #<SB-SYS:FD-STREAM for "a constant string" {C6F56C1}>) ("server-pr$ 21: (TBNL::LISTEN-FOR-REQUEST #<SB-SYS:FD-STREAM for "a constant string" {C6F56C1}> TBNL::PROCESS-REQUEST) 22: ((LAMBDA NIL))

4 7

[tbnl-devel] Flexi-streams needs a change for openmcl
by ocorrain＠yahoo.com 03 Oct '06

03 Oct '06

Hi-- OpenMCL runs into some problems with having +latin-1+ defined as a constant, since external-format doesn't have a load-form defined. I've added make-load-form to external-format.lisp in flexi-streams, thusly: --- external-format.lisp~ 2006-06-13 00:26:12.000000000 +0100 +++ external-format.lisp 2006-10-03 17:27:15.000000000 +0100 @@ -54,6 +54,15 @@ (:documentation "EXTERNAL-FORMAT objects are used to denote encodings for flexi streams.")) +(defmethod make-load-form ((self external-format) &optional env) + (declare (ignore env)) + `(make-instance 'external-format + :name ,(external-format-name self) + :id ,(external-format-id self) + :little-endian ,(external-format-little-endian self) + :eol-style ,(external-format-eol-style self))) + + (defun make-external-format% (name &key (little-endian *default-little-endian*) id eol-style) "Used internally by MAKE-EXTERNAL-FORMAT." -- Tiarnán

2 2

[tbnl-devel] Add hook before uploading a file.
by Erik Enge 02 Oct '06

02 Oct '06

My users will upload files as large as 500M to my servers. This will of course take awhile and I think it's asking for trouble to let them submit and then just let the browser sit there and spin a currently-working-cursor without any other feedback. So, I use an IFRAME and some Ajax to submit the form and also poll to see how the submittion is coming along. Then I report this to user in the form of a progress-bar. (Lots of examples of this, just search for "ajax upload progress" in Google.) Anyway, by default in TBNL, as far as I can tell, the request doesn't hit my code until after the file has been uploaded. What I think I really need instead is to have access to the temporary filename created for the upload (so I can track its size) right before TBNL starts reading the file. I've put this together locally by creating a hook in MAKE-TMP-FILE-NAME[1] which is simply called with the tmp-file-name created before returning. In my code I then use this filename to create data for the progress-bar. My question is whether there's a better way to achieve this and/or whether or not you want a patch. Thanks, Erik. [1] I think a comment explaining that it's called from the RFC2388 code would've been really helpful. :-)

3 6