tbnl-devel April 2005

tbnl-devel@common-lisp.net

5 participants
13 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] *apache-port* changed to *tbnl-port*
by Lukas Trejtnar 27 Apr '05

27 Apr '05

Hi I upgraded to a new version of Lispworks and consequently to a new version of TBNL and discovered that my application didn't work anymore. I found after a while that the variable *apache-port* was renamed to *tbnl-port*. How can I track these significant (for me) changes? I think I didn't find this change in an archive of this mailing list. Thanks Lukas

2 1

[tbnl-devel] New version 0.5.5
by Edi Weitz 18 Apr '05

18 Apr '05

ChangeLog: Version 0.5.5 2005-04-18 Make RFC 2388 code an external dependency (thanks to Janis Dzerins) Download: <http://weitz.de/files/tbnl.tar.gz> Cheers, Edi.

1 0

Re: [tbnl-devel] tbnl / sbcl 0.8.21
by Edi Weitz 06 Apr '05

06 Apr '05

On Wed, 6 Apr 2005 15:43:52 -0700, Keith Irwin <keith.irwin(a)gmail.com> wrote: > en_US.UTF-8 If you currently don't need full Unicode support then maybe (where are the SBCL experts?) it suffices to change this to "en_US.ISO-8859-1" (or whatever it's called) before starting SBCL. > Yeah. Okay. > > I changed stuff in rfc2238 and araneida to use unsigned-byte 8 in a > few with-open-files and that solves the compilation problem. > Serving images is a different story, and I imagine if I use unicode > chars in my content I'd get a similar prob. > > My current option is to serve the images using apache (an Alias in > the config), but I tend to like to have apps that require a minimum > of os-level config (until they're big enough to warrant that sort of > thing). > > I might play with it tomorrow a bit more. I basically agree with you that it's nice to have everything served by the Lisp image. However, this is almost impossible unless you have bivalent streams. (It is my understanding that SBCL will have them sooner or later because the need is obvious.) Also, note that Apache is pretty good at serving static content. As far as serving full Unicode content is concerned you'll actually want more than bivalent streams - you want to have (socket) streams that can change their character encoding on the fly. AFAIK only CLISP (not supported by TBNL) and AllegroCL can do that at the moment. But look at the Unicode example in test.lisp for an example on how this can be done in LW with implementation-specific features. Cheers, Edi.

2 1

[tbnl-devel] tbnl / sbcl 0.8.21
by Keith Irwin 06 Apr '05

06 Apr '05

Folks-- I believe Edi forwarded a message I'd written about some sort of byte-related encoding problems (or decoding) with regard to SBCL. The problem occurs when I want to serve up an image file as part of, say, a background for a web site. Does anyone want to focus my attention on any particular files, or areas to envistigate, or should I just leave well enough alone because you all are about ready to update the code? Edi's comment: > One solution might be to check if SBCL has some kind of default > external format which can be used to overwrite the UTF-8 format. I > don't use SBCL myself but I seem to remember that this might depend on > the value of some environment variable when the image is started. > Maybe someone else here knows the details. > Another option would be to treat SBCL like LW and AllegroCL in case it > also has bivalent streams. Since I'm not a developer of TBNL nor do I intend to be, I'm not sure what the above means. Is the problem that TBNL is trying to read a binary file into, uh, characters, or something? Anyway, I'll see if I can't come up with a hack and then drop it here in case it'll help an expert get a real fix in quicker. Thanks, Keith

2 1

[tbnl-devel] Re: tbnl / sbcl 0.8.21
by Edi Weitz 05 Apr '05

05 Apr '05

[Please use the mailing list. Thanks.] Hi! On Tue, 05 Apr 2005 12:07:22 -0700, Keith Irwin <keith(a)keithirwin.com> wrote: > Sir-- Woops... > I encountered the following after attempting to install TBNL via > asdf-install on SBCL 0.8.21. > > SBCL: linux, sb-thread, sb-unicode > > My guess is that it has something to do with SBCL defaulting streams > to unicode rather than some previous way of doing things, but I > don't really know much about that stuff. > > Thought you might like to know. > > Keith > keith(a)keithirwin.com > > > ; compiling (DEFUN SEND-FILE ...) > ; compiling (DEFPARAMETER *HEADLINE* ...) > ; compiling (DEFUN MENU ...) > ; compiling (SETQ *DISPATCH-TABLE* ...) > > ; /home/keith/.sbcl/site/tbnl-0.5.4/test/test.fasl written > ; compilation finished in 0:00:01 > STYLE-WARNING: redefining TBNL-LINK in DEFUN > STYLE-WARNING: redefining MENU-LINK in DEFUN > STYLE-WARNING: redefining AUTHORIZATION-PAGE in DEFUN > > debugger invoked on a SB-INT:STREAM-DECODING-ERROR in thread 10326: > decoding error on stream > #<SB-SYS:FD-STREAM for "file > \"/home/keith/.sbcl/site/tbnl-0.5.4/test/fz.jpg\"" {936DAA1}> > (:EXTERNAL-FORMAT :UTF-8): > the octet sequence (255 216 255 224) cannot be decoded. > > Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. > > restarts (invokable by number or by possibly-abbreviated name): > 0: [ATTEMPT-RESYNC ] Attempt to resync the stream at a character > boundary > and continue. > 1: [FORCE-END-OF-FILE] Force an end of file. > 2: [RETRY ] Retry performing #<ASDF:LOAD-OP NIL {A0DBFD9}> > on > #<ASDF:CL-SOURCE-FILE "test" {9AB5861}>. > 3: [ACCEPT ] Continue, treating #<ASDF:LOAD-OP NIL > {A0DBFD9}> on > #<ASDF:CL-SOURCE-FILE "test" {9AB5861}> as > having been > successful. > 4: [RETRY ] Retry installation > 5: [ABORT ] Exit debugger, returning to top level. > > (SB-INT:STREAM-DECODING-ERROR > #<SB-SYS:FD-STREAM for "file > \"/home/keith/.sbcl/site/tbnl-0.5.4/test/fz.jpg\"" {936DAA1}> > (255 216 255 224)) > 0] One solution might be to check if SBCL has some kind of default external format which can be used to overwrite the UTF-8 format. I don't use SBCL myself but I seem to remember that this might depend on the value of some environment variable when the image is started. Maybe someone else here knows the details. Another option would be to treat SBCL like LW and AllegroCL in case it also has bivalent streams. HTH, Edi.

1 0

[tbnl-devel] New version 0.5.4 (Was: New version 0.5.3)
by Edi Weitz 03 Apr '05

03 Apr '05

On Sun, 3 Apr 2005 11:17:55 -0400, Bob Hutchison <hutch(a)recursive.ca> wrote: > Thanks for the new release. There's just one small problem that I > can see. In the function listen-for-request in modlisp.lisp there is > a loop where you set *use-mod-lisp-headers* -- this is a > misspelling, it should be *use-modlisp-headers* (and until I > corrected this I was getting some bad behaviour). Argh! That happens if you think you can type faster than slime-complete-symbol... :( I've uploaded a corrected version (0.5.4). Thanks and sorry for the noise, Edi.

1 0

[tbnl-devel] New version 0.5.3
by Edi Weitz 03 Apr '05

03 Apr '05

ChangeLog: Version 0.5.3 2005-04-03 Re-introduced automatic front-end selection (originally by Bob Hutchinson) Download: <http://weitz.de/files/tbnl.tar.gz> Have fun, Edi.

1 0

Re: [tbnl-devel] basic package question
by Edi Weitz 02 Apr '05

02 Apr '05

On Sat, 2 Apr 2005 10:18:56 -0500, Jason Wang <randomtalk(a)gmail.com> wrote: > since i can use (asdf:oos 'asdf:load-op :tbnl-test) to start up > tbnl-test package, i thought i'd use the same statment: (asdf:oos > 'asdf:load-op :test2) to fire up teh test2 package, apparently it > doesn't work.. can you tell me what i'm doing wrong? ASDF is not used to "start up" or "fire up" packages but to load libraries. You might want to look at the ASDF documentation or at my ASDF-INSTALL tutorial. If you just want to serve pages other than the ones from the test website with TBNL you don't necessarily need a new package and you don't need ASDF either. Instead, you should read the documentation about handlers and dispatchers: <http://weitz.de/tbnl/#handlers> You can change these values while TBNL is already running. Cheers, Edi.

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

tbnl-devel April 2005