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

[hunchentoot-devel] asterisk
by Dmitri Hrapof 21 May '09

21 May '09

And while I'm at it: why, oh why have you added "*" to those methods? To make people recheck their code's compatibility with new Hunchentoot? BTW, I like the idea of easy-handlers very much. I've been making similar macros for quite a while, and I wonder: do you plan to add to CL-WHO some machinery to reuse these "function arguments"? I mean, often (at least for me) web page contains a form with action pointing to the same page, and it's rather boring to write (:input :type "text" :name "arg1" :value arg1) etc. Again, I have some macros for that, but rather unpolished.

3 7

[hunchentoot-devel] *supports-threads-p*
by Dmitri Hrapof 21 May '09

21 May '09

Hello! If I load Hunchentoot 1.0.0 into ClozureCL, CCL says that *supports-threads-p* is undefined, would you like to use bt:*supports-threads-p* instead? The reason, it seems, is that CCL doesn't like symbol-macro *supports-threads-p* being defined in the same file it's being used. If I move it into e.g. compat.lisp, everything is fine. Cheers, Dmitri

3 3

[hunchentoot-devel] Webpage documentation for REDIRECT function
by Jim Prewett 21 May '09

21 May '09

Hello, I was looking at the Hunchentoot webpage documentation for the REDIRECT function and noticed that it lacked information about what the ADD-SESSION-ID keyword argument does. This information is available in the documentation string for the function (which says "Adds a session ID if ADD-SESSION-ID is true."). Whaddya think about adding that to the webpage as well? Jim James E. Prewett Jim(a)Prewett.org download(a)hpc.unm.edu Systems Team Leader LoGS: http://www.hpc.unm.edu/~download/LoGS/ Designated Security Officer OpenPGP key: pub 1024D/31816D93 HPC Systems Engineer III UNM HPC 505.277.8210

2 1

[hunchentoot-devel] redirect problems
by Tiarnan O'Corrain 07 May '09

07 May '09

Hi-- I have a login form on the front page of a site that uses (say) /login.html as its 'action'. Login.html just looks at the post parameters, tries to log the user in, and redirects to the front page, which should then display user specific information. However, the front page displays the old login form, and requires a refresh to pick up the new information. Ditto with logout, which shows the user information until the page is refreshed. I'm using hunchentoot:redirect with the URL, and can't figure out why this isn't working. Any ideas? thanks Tiarnan -- difficile est saturam non scribere

2 1

[hunchentoot-devel] Using json-rpc and Hunchentoot
by Brett van de Sande 09 Apr '09

09 Apr '09

I am developing a Hunchentoot server that communicates using json-rpc 2.0. The default Hunchentoot error messages are html formatted and I need to make a json-rpc version of these messages. I see that I can use *http-error-handler* to make a custom error message for a given error code in whatever format I like. That works just fine. However, the default Hunchentoot error messages have additional (important) information, such as the actual lisp error message for a lisp error. (This is given in the "content" argument of the function "start-output" in headers.lisp.) I need to be able to include this additional information in my json-rpc formatted error messages. How would I do this? Brett van de Sande

3 3

[hunchentoot-devel] New releases of Hunchentoot, Drakma, and Chunga
by Edi Weitz 09 Apr '09

09 Apr '09

Hi, I've just released new versions (all called 1.0.0) of Hunchentoot, Drakma, and Chunga. Note that none of these is compatible with earlier versions, so if you upgrade, you'll need to upgrade all of them. If you're using Hunchentoot or Drakma in a production environment and if it works well for you, you probably shouldn't switch. These are releases with a lot of changes and it is pretty likely that they contain bugs. If you're tracking the development, it'd be nice if you could download the new versions and provide feedback, though. The good news: * Hunchentoot has a new architecture that should hopefully make it much easier to extend or to customize it. * Both Huchentoot and Drakma should be faster now. * Now that we finally have release versions again, there are more things to come. Expect 1.0.1, 1.0.2, etc. releases in the next weeks. The bad news: * The Hunchentoot API has changed considerably and you'll have to read the documentation to see how it works now. Of course, we didn't do that to annoy you - we have to change our own web apps as well. We think that the new API is better, though, and that the change was worth it. * Some stuff has been removed, either because it seemed that nobody used it or because we thought it didn't really belong into a web server. Have fun, Edi.

10 31

[hunchentoot-devel] Using Hunchentoot and cl-who with other people (non-coders)
by Larry Clapp 02 Apr '09

02 Apr '09

Hi, list, I am developing my first web app of any kind. I've no experience with other web app frameworks (like RoR or what have you). I am working with a friend, who knows Dreamweaver and other fairly high level web-design tools, but can't code at all. On the other hand, I don't know web-design at all, using tools or not, so we're pretty complementary. So I'm seeking guidance on how I can continue to develop using Hunchentoot and cl-who, and yet integrate machine-generated html or css or what have you from Dreamweaver or other tools? As I understand it, this is a known difficulty that other teams and tool designers have faced, and if I'd ever worked with any other teams or tools then it might be a no-brainer, but given my lack of experience in this respect I'm not even sure what to Google to find answers for myself. I'd appreciate any advice, links, pointers, etc, that users of Hunchentoot and/or cl-who could provide. Thanks! -- Larry Clapp

8 10

[hunchentoot-devel] Test, please ignore
by Hans Hübner 31 Mar '09

31 Mar '09

Tracking down a delay problem.

2 2

None
by None 14 Mar '09

14 Mar '09

1 0

[hunchentoot-devel] Tracking file upload progress
by Andrei Stebakov 14 Mar '09

14 Mar '09

With the old hunchentoot I was able to get the flexi-stream of the request using (content-stream request) and then when my ajax handler wanted to update the upload progress it would read (flexi-stream-position of the stream that I kept in a session). With the new hunchentoot this doesn't work. I realize that (content-stream request) is not a flexi-stream, so when I save a stream in my session I make a flexi-stream using (make-flexi-stream (hunchentoot::content-stream request) :external-format hunchentoot::+latin-1+). Then when ajax handler reads flexi-stream-position of the saved stream I always get 0. What am I missing? Thank you, Andrei

1 0