tbnl-devel July 2005

tbnl-devel@common-lisp.net

4 participants
6 discussions

[tbnl-devel] arbitrary per-request data?
by Zach Beane 17 Sep '05

17 Sep '05

I have an application that has a notion of a current user that is lazily established on a per-request basis. For now, I have been returning a handler that is really a lambda wrapping a real handler that lexically binds the special *current-user*: (defun page-handler (request) (multiple-value-bind (handler foundp) (gethash (script-name request) *handlers*) (when foundp (lambda () (let ((*current-user* *current-user-local-unbound-value*)) (funcall handler)))))) But it occurred to me that there is already the *request* structure. Would it make sense to be able to have a table of arbitrary keys and values in the request structure for application use? I was thinking of an accessor like this: request-data key &optional (request *request*) => value, foundp Then I could write CURRENT-USER something like: (defun current-user () (multiple-value-bind (value foundp) (request-data 'user) (if foundp value (setf (request-data 'user) (cookie-user))))) Right now it's a bit messier than that. What do you think? If this seems reasonable I can work out and submit a patch. Zach

3 5

[tbnl-devel] New version 0.5.0 / Multiple back-ends
by Edi Weitz 17 Aug '05

17 Aug '05

Hi! I've finally found some time to incorporate Bob's changes, test them and document them. I've also changed the logging API and re-factored some of the code. I'm sure I broke something in the process so please test... :) Specifically, I tried to explain in the documentation how TBNL talks with the different back-ends. I also changed the test setup so that it now hopefully adapts to all three back-ends and gives new users a chance to understand how TBNL works. While testing the "stand-alone" version I had some problems with MS Internet Explorer but I /think/ I've nailed them down now. Note that some of the changes in 0.5.0 might break API compatibility with earlier versions so be careful if you use this release for an existing deployment of TBNL and resort to the docs if in doubt. Special thanks to Bob Hutchison who made this all possible! Download: <http://weitz.de/files/tbnl.tar.gz>. Have fun, Edi.

4 6

[tbnl-devel] Upload of text files
by Jaroslaw.Tomczak＠sanofi-aventis.com 02 Aug '05

02 Aug '05

Hi, I have noticed a minor problem when uploading text files with TBNL (version 0.5.5 + Apache 2.0.54 + mod_lisp2 + LispWorks 4.4.5, all on Windows 2000) -- DOS/Windows text files (CR/LF) have one empty line appended at the end when uploaded. Unix text files, however, are transferred correctly. Any ideas? Jaroslaw Tomczak P.S. Edi, thanks for your great libraries! -- Dr. Jaroslaw Tomczak Aventis Pharma Deutschland GmbH A company of the sanofi-aventis group SMA Chemical Sciences Drug Design I Industriepark Hoechst, H840 room 104 D-65926 Frankfurt / Main phone: +49 (69) 305-14710 fax: +49 (69) 305-13068

2 2

[tbnl-devel] UTF-8 problems -- patch
by Ivan Shvedunov 28 Jul '05

28 Jul '05

Hello. Well, I've promised this patch somewhat earlier, but I didn't have time to complete it... I've discovered several problems with TBNL's handling of UTF-8. Namely, there was a problem with url-decode in util.lisp which was turning UTF-8 urlencoded strings into something incomprehensible, and also there was problem with Content-Length in modlisp.lisp which was causing UTF-8 content to be truncated. The attached patch works only with SBCL. I mean that it shouldn't break other Lisps, but proper unicode hanling is implemented only for SBCL. I've tried to make it work with Allegro demo/LispWorks Personal Edition, but with no luck. Well, concerning Allegro, the problem here is that sockets that are used to talk to mod_lisp are set to latin-1 encoding for some reason, most likely KMRCL needs to be fixed a bit, again, unfortunatelly I just have no time to complete this. As of LispWorks, I just don't know how to turn a string into series of octets and vice versa using current encoding - i.e. I didn't find something like Allegro/SBCL octets-to-string/string-to-octets there. Concerning implementation - I've introduced :tbnl-unicode feature that is set for supported Unicode-aware Lisps in specials.lisp (I'm setting it for Allegro and SBCL, thogh it doesn't help Allegro much). Also I've added supporting funcs, bytes-to-string and string-to-bytes (defined only when #+tbnl-unicode) that do the dirty job of string conversion. Ivan

2 3

[tbnl-devel] (no subject)
by Bob Hutchison 14 Jul '05

14 Jul '05

Hi, So far I've got 48 create-static-file-dispatcher-and-handler definitions in my TBNL dispatch table. These are mostly image files now, but also CSS and javascript files. This number is about to go up by maybe five or six real soon now. Then soon after that I'll need to be able to serve an unknown, but large, number of files of different types. Is there currently a dispatcher/handler that deals with directories, possibly even recursively, or maybe that consults some kind of list of things to serve? No point writing one if it is already done. If there isn't one already, I'll code one up and contribute it to TBNL. Cheers, Bob ---- Bob Hutchison -- blogs at <http://www.recursive.ca/hutch/> Recursive Design Inc. -- <http://www.recursive.ca/>

3 5

AW: [tbnl-devel] Upload of text files
by Jaroslaw.Tomczak＠sanofi-aventis.com 05 Jul '05

05 Jul '05

Hi Edi, yes it seems to work for me. Thank you! Jaroslaw > -----Ursprüngliche Nachricht----- > Von: Edi Weitz [mailto:edi@agharta.de] > Gesendet: Dienstag, 5. Juli 2005 13:08 > An: Tomczak, Jaroslaw PH/DE > Cc: tbnl-devel(a)common-lisp.net > Betreff: Re: [tbnl-devel] Upload of text files > > > Hi! > > On Mon, 4 Jul 2005 13:24:54 +0200, > <Jaroslaw.Tomczak(a)sanofi-aventis.com> wrote: > > > I have noticed a minor problem when uploading text files with TBNL > > (version 0.5.5 + Apache 2.0.54 + mod_lisp2 + LispWorks 4.4.5, all on > > Windows 2000) -- DOS/Windows text files (CR/LF) have one empty line > > appended at the end when uploaded. Unix text files, however, are > > transferred correctly. > > Thanks for the report, I wasn't aware of this. > > > Any ideas? > > I sniffed around a bit and it looks like the problem is in the RFC > 2388 library TBNL uses. As a workaround try to replace the part of > rfc2388.lisp which looks like > > (3 ;; first dash in dash-boundary > (cond ((char= char #\-) > (enqueue-char) > (setq state 4)) > (t > (write-queued-chars) > (write-char char result) > (setq state 1)))) > > with this one: > > (3 ;; first dash in dash-boundary > (cond ((char= char #\-) > (enqueue-char) > (setq state 4)) > ((char= char #\return) > (write-queued-chars) > (enqueue-char) > (setq state 2)) > (t > (write-queued-chars) > (write-char char result) > (setq state 1)))) > > I haven't really tested if this breaks anything else but at least it > seems to get rid of your problem. Let me know if it works for you. > > I'll send a bug report to Janis. > > > P.S. Edi, thanks for your great libraries! > > You're welcome. > > Cheers, > Edi. >

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

tbnl-devel July 2005