[hunchentoot-devel] A couple of issues in Hunchentoot 1.0.0
Hi list, Thank you very much for your work on Hunchentoot. It's one of my top Lisp tools! After upgrading to 1.0.0 and trying to port and run some of my apps I found several issues, which might use some looking at :) - stream returned by send-headers is binary now. It used to be a flexi stream.It might be worth mentioning in the documentation that it's necessary to wrap it in flexi stream to write character sequences - do-sessions is gone and *session-db* is internal to hunchentoot - *catch-errors-p* is gone and *http-error-handler* is called with HTTP code only (for error page customisation only?). Not-catching lisp errors by hunchentoot was excellent for debugging - calling reset-sessions outside of request context complains about *acceptor* not being set Thanks again, and all the best to you :) Best Regards, /S
Hi Slawek, On Thu, Feb 26, 2009 at 7:25 PM, Slawek Zak <slawek.zak@gmail.com> wrote:
stream returned by send-headers is binary now. It used to be a flexi stream.It might be worth mentioning in the documentation that it's necessary to wrap it in flexi stream to write character sequences
The docstring already says that the stream returned is binary. But, yeah, one might add a sentence about flexi streams.
do-sessions is gone and *session-db* is internal to hunchentoot
Yes, see the section about customizing session behaviour. You can insert your own session-db method. Or, if you absolutely want to iterate globally across all sessions, you can catch the return value of the default method.
*catch-errors-p* is gone and *http-error-handler* is called with HTTP code only (for error page customisation only?). Not-catching lisp errors by hunchentoot was excellent for debugging
See the recent discussion on the list. The next release will provide some changes w.r.t. error handling and debugging.
calling reset-sessions outside of request context complains about *acceptor* not being set
Yes, that's a consequence of making the session behaviour customizable. Is this a big problem? Thanks for the feedback, Edi.
do-sessions is gone and *session-db* is internal to hunchentoot
Yes, see the section about customizing session behaviour. You can insert your own session-db method. Or, if you absolutely want to iterate globally across all sessions, you can catch the return value of the default method.
Right.
*catch-errors-p* is gone and *http-error-handler* is called with HTTP code only (for error page customisation only?). Not-catching lisp errors by hunchentoot was excellent for debugging
See the recent discussion on the list. The next release will provide some changes w.r.t. error handling and debugging.
Much appreciated.
calling reset-sessions outside of request context complains about *acceptor* not being set
Yes, that's a consequence of making the session behaviour customizable. Is this a big problem?
No really. I just have to remember to store the acceptor on a side to be able to reset sessions ;) Thanks, /S
participants (2)
-
Edi Weitz -
Slawek Zak