tbnl-devel December 2009

tbnl-devel@common-lisp.net

10 participants
12 discussions

[hunchentoot-devel] maybe bug + patch
by Richard KLINDA 06 Jun '10

06 Jun '10

Hello, I may have found a bug. After stopping an acceptor with STOP, one can't start it again with START, because the START method doesn't reset the value of acceptor-shutdown-p to NIL, so the listener returns/quits instantly. See the attached trivial patch, that fixes the issue for me, but maybe I'm just missing something here. -- Richard

3 2

[hunchentoot-devel] PATCH: Some minor fixes for cl-webdav under hunchentoot 1.0
by Matthew Curry 21 Feb '10

21 Feb '10

Edi, I took a look at it tonight anyway, and there where some obvious minor fixes I spotted right away, attached is a patch that gets (using cadaver) an initial connection, a put, and a get to work. Just functions that were renamed in the new hunchentoot. Delete doesn't work, complains about a handler-done tag being unknown (but thrown). Here's the message log entry: [2009-11-15 20:55:06 [ERROR]] attempt to THROW to a tag that does not exist: HANDLER-DONE I'm not too familiar with older versions of hunchentoot, does that ring a bell for you? I'll keep looking. -Matt

3 15

[hunchentoot-devel] Imminent release
by Edi Weitz 27 Dec '09

27 Dec '09

Hi, I've made a couple of changes tonight (notably adding *catch-errors-p* and *log-lisp-backtraces-p* back in and exposing a new function handle-request along the lines of Frode's suggestions). I'm planning to make a new release in the next days based on what's in the BKNR repository right now. I've only tested on LispWorks so far (and I have no plans to test on other Lisps for now). If you find any obvious errors, please let me know. Also, if you've provided code in the last months which made it into the upcoming release but aren't mentioned in the changelog, let me know as well. My apologies for having been pretty passive with Hunchentoot in the last months, but there were (and still are) too many other things to do. Thanks, Edi.

1 0

[hunchentoot-devel] Backtrace display
by Jonathon McKitrick 27 Dec '09

27 Dec '09

I recall some time ago, the break and backtrace capability of Hunchentoot was removed, perhaps to make it less platform dependent. But I still find myself often trying to find the origin of cryptic error messages, and adding FORMAT and BREAK statements to narrow down the problem area. What is a good way to drop in support for, say, SBCL, so that an error will break into the debugger with a backtrace, or even dump the backtrace to the log file? -- Jonathon McKitrick

7 9

[hunchentoot-devel] Specializing process-request
by frode＠netfonds.no 22 Dec '09

22 Dec '09

Hi all, The Hunchentoot documentation at http://weitz.de/hunchentoot/ mentions that an around-method on process-request "might be a good place to introduce around methods which bind special variables or do other interesting things." In my eyes there's a problem with this, because the standard process-request sets up crucial parts of the dynamic environment for request processing, and around methods can only modify the scope outside of that. In particluar, error and warning conditions are handled before the around method gets a chance to intervene. I would suggest adding a new generic function that does just the dispatching, i.e. something like this: (defmethod dispatch-request ((*request* t)) (funcall (acceptor-request-dispatcher *acceptor*) *request*)) ..and have the kernel of the standard process-request method just call dispatch-request in the obvious way. I think this is a more appropriate configuration point for the request processing protocol than the current process-request is. (I can/could of course specialize process-request for my acceptor class using an unqualified method, and thus set up the dynamic environment just how I want it. However I would then just have to copy the full body of the standard process-request to insert a line or two inside the body of the handler-bind. I believe it's the purpose of a processing protocol to avoid having to do such things.) -- Frode V. Fjeld Netfonds Bank ASA

3 6

[hunchentoot-devel] updated version
by John Thingstad 22 Dec '09

22 Dec '09

Where is the the current SVN version of Hunchentoot that you are working on located? It seems the huncentoot version at www.weitz.de hasn't been updated in ages.

7 9

[hunchentoot-devel] Hunchentoot on Clozure windows x86
by Seth 19 Dec '09

19 Dec '09

Im trying to get hunchentoot to run on windows vista. Everything compiles successfully and i downloaded opensll and installed dlls into the system directory. However, when i type the following into emacs (hunchentoot:start (make-instance 'hunchentoot:acceptor :port 4242)) (hunchentoot:define-easy-handler (say-yo :uri "/yo") (name) (setf (hunchentoot:content-type*) "text/plain") (format nil "Hey~@[ ~A~]!" name)) and go to http://127.0.0.1:4242/yo, i see a blank page. In fact, i can go to /anything and still see a blank page, even though it should (?) produce an error since that page wasn't defined. So what should i do to start debugging this? Thanks! ---- Msg sent via WebMail

2 1

[hunchentoot-devel] Controlling file uploads with hunchentoot
by Semion Prihodko 16 Dec '09

16 Dec '09

Hi, guys. I have the folowing question. Is there a posibility to check multipat/form-data request format before uploading files? I would like to write request handler which can check name and MIME of next file to be uploaded to have a possibility to abort request processing without wasting server resources while uploding huge files. The *upload-file-hook* doesn't help here because it cannot give a name and MIME of current file. What can you suggest me? Thanks in advance.

3 13

[hunchentoot-devel] When to use with-html-output and when to use with-html-output-to-string
by Phil Marneweck 16 Dec '09

16 Dec '09

When should one use with-html-output and when should one use with-html-output-to-string?

3 3

[hunchentoot-devel] Hunchentoot Recursive Function
by Phil Marneweck 16 Dec '09

16 Dec '09

This is most likely a problem with my understanding of lisp and not hunchnetoot. Why does the following function only out put "Recursive count- 0" to the hunchentoot page? (defun recursive-test (count) (with-html-output-to-string (*standard-output*) (if (< count 10) (recursive-test (+ count 1))) (str (format nil "Recursive count- ~A" count)))) (define-easy-handler (test-recursive :uri "/test.html" () (with-html-output-to-string (*standard-output*) (str (recursive-test 0))))

3 5

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

tbnl-devel December 2009