tbnl-devel September 2004

tbnl-devel@common-lisp.net

5 participants
6 discussions

[tbnl-devel] Handling HTTP errors
by Stefan Scholl 01 Mar '05

01 Mar '05

Hi! Function send-output in modlisp.lisp handles the response for different return codes. E. g. there's a "The requested URL ~A was not found on this server." for the 404 (+http-not-found+). How about letting the user change this behavior? One could explain the error to the user. Maybe in another language. Or think of all the funny 404 games. Remember the SGI babies? There could be different approaches: * Simple hash A hash with error code as key and handler as value. + Easy to implement + Can handle all errors (thrown by handlers _and_ when no dispatcher is found) - Not very flexible. Just checks for the code and not for any request data. * Error dispatcher Like the normal dispatcher, but checking for the right error output handler. + Can handle all errors (thrown by handlers _and_ when no dispatcher is found) + Flexible. Can check the code _and_ request data. - A bit big. The same effort like handling normal requests. * Handler outputs itself and signals that A handler wants to return a 404. It constructs the output string and signals the fact that there's no need for TBNL to build the HTML for the output. + Easy to implement(? clean?) + Flexible - Can't handle all errors. (No handler found? Then the code won't be executed.) Regards, Stefan

2 3

[tbnl-devel] mod_lisp2-2.c
by Massimiliano Campagnoli 07 Sep '04

07 Sep '04

I am not able to reproduce a crash on Apache 2 using mod_lisp2-2.c and TBNL. As soon as I found a way I'll post to the list. Actually I would be very interested in using TBNL on mod_lisp2-2.c if it is kept at the same latest level of mod_lisp.c 2.38 with latest Edi's fixes. -- ING. MASSIMILIANO CAMPAGNOLI PAOLO ASTORI SRL VIA MIRABELLA, 9 28013 - GATTICO ITALY

1 0

[tbnl-devel] Problems with SBCL 0.8.14
by Stefan Scholl 06 Sep '04

06 Sep '04

Is anybody testing TBNL with SBCL 0.8.14, too? I get the following with start-session (debugged the old way, due to the lack of backtrace): [Tue Aug 31 15:17:24 2004] [error] [TBNL] segmentation violation at #X985B0F0 I've inserted some (log-message :debug "....") to find the error. It reaches the "before start-session", but not the "after start-session" marker. OK, I see if I can find something in TBNL. I really think this is more a bug in SBCL and I don't have to find a solution for TBNL. Instead I have to find a test case for SBCL. Regards, Stefan

3 7

Re: [tbnl-devel] Help needed in handler function with (sleep seconds)
by Massimiliano Campagnoli 05 Sep '04

05 Sep '04

Stefan is perfectly right. mod_lisp2-3.c has some problem in managing timeout. where mod_lisp2-2.c (which is based on a different implementation) works has expected if the handler contains (sleep n). But since mod_lisp2-2.c occasionally crashes Apache and has no support for the latest Edi's improvements (since is based on mod_lisp 2.33) I would say that the option to move back to apache 1.3 with the latest mod_lisp.c 2.38 is still a good move, until someone (Marco Antoniotti & Co.) with enough experience has time to port and test mod_lisp.c 2.38 to Apache2. Stefan Scholl wrote: >On 2004-08-23 17:21:14, Edi Weitz wrote: > > >>>mod_lisp for apache 2 >>> >>> >>There are several versions as far as I know. >> >> > >Hmm. >http://www.fractalconcept.com:8000/public/open-source/mod_lisp/contrib/mod_… >has a timeout of 1 second and all ap_reset_timeout() and >ap_kill_timeout() calls are commented out. > >Haven't tried to understand the code, though. Just searched for >"timeout". > > >Regards, >Stefan > > > >_______________________________________________ >tbnl-devel site list >tbnl-devel(a)common-lisp.net >http://common-lisp.net/mailman/listinfo/tbnl-devel > > > -- ING. MASSIMILIANO CAMPAGNOLI PAOLO ASTORI SRL VIA MIRABELLA, 9 28013 - GATTICO ITALY

2 1

[tbnl-devel] (post-parameters) strange behaviour ?
by Massimiliano Campagnoli 02 Sep '04

02 Sep '04

Try to handle this html form: <html> <body> <form name="my-form" action="/tbnl/form" method="post"> <input type=text name=":myfield" value="foo"> </form> </body> </html> after submitting this form in TBNL *debug-mode* you will get: > (post-parameters) > (("%3Amyfield" . "foo")) instead of >(("myfield" . "foo" )) Any explanation for this ? -- ING. MASSIMILIANO CAMPAGNOLI PAOLO ASTORI SRL VIA MIRABELLA, 9 28013 - GATTICO ITALY

3 3

[tbnl-devel] File Upload Design Issues
by Jeff Caldwell 01 Sep '04

01 Sep '04

The code Edi referred to is only a proof of concept at the moment. Don't bother looking at it yet. (See below.) It did let me upload a file. I'm happy to look at it again, though. There are things I need to research, and I am asking for everyone's help and advice so that I get the code as right as possible: 1) What are the relevant RFC's I need to consider? 2) What references/URLs/sample code is available for me to learn about the encoding/stream issues? 3) General comments on the design. In particular, uploading a file may only the first step. What is to be done with the file? 3a) There are OS dependencies, as not all OS's support the same file names. 3b) The file upload must generate a portable but unique internal name while at the same time retaining the OS-specific name specified by the sender (original name). 3c) This implies a kind of catalog of files, mapping the original name to the internal name and vice versa. This technique also is necessary to prevent duplicate file names, for example from multiple users. 3d) The user should be able to associate a short and/or long description, and possibly a category or two, with the file. TBNL might not dictate this precisely but the catalog should be flexible in what it holds. 3e) The catalog needs to be able to associate a file with a user and vice versa. Users aren't a TBNL concept at the moment and I'm not sure adding them just for this is worthwhile. On the other hand, uploading and storing files without the possibility of a sense of ownership doesn't seem robust. Is this really a part of the TBNL core? How can this be handled cleanly? 3f) Where and how should the files be stored? ACS and OpenACS (openacs.org), the last time I looked, store uploaded files in a big directory tree with, IIRC, subdirectories named with single letters. The destination subdirectory was chosen by the first 3 or 4 chars of the internally-generated file name. The idea is that a filesystem can have, or can efficiently handle, only so many files per subdirectory. Given an idea of the total number of uploaded files we want to support, we could calculate the depth and number of subdirectories needed. 3g) TBNL-level security is enough and it's OK to mix uploaded files from several users in the same catalog and subdirectories, so long as TBNL keeps things sorted out and, depending upon the application, the programmer is responsible for showing/making available the right file to the right person. I bet I both left something out and put too much in :) I'd appreciate comments on all of the above. In summary, how should the files be stored and how should the catalog be structured? Once I have an idea of how we think this should work, I'm happy to glue it all together. Thanks for your help. Jeff --- Edi Weitz <edi(a)agharta.de> wrote: > On Mon, 30 Aug 2004 17:19:17 -0500, Travis Cross > <travis(a)crosswirecorp.com> wrote: > > > I have one question that I haven't seen come up on > the mailing list > > or in the documentation: what are the hurdles or > considerations in > > implementing multipart form / file upload handling > in TBNL ? > > See Stefan's reply. My main problem is time. I > haven't even found the > time to read through all the relevant RFCs. I also > think that streams > (changing the encoding on the fly) might be an issue > here. > > This feature will probably have to wait until I need > it in a project > or until someone else provides a working patch. > > You might want to look at Jeff Caldwell's code at > tbnl.org - I seem to > remember that he had started working on this. Jeff? > > Cheers, > Edi. > _______________________________ Do you Yahoo!? Win 1 of 4,000 free domain names from Yahoo! Enter now. http://promotions.yahoo.com/goldrush

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

tbnl-devel September 2004