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

[hunchentoot-devel] edicl & Quicklisp - formal release tarballs or production-ready master branches?
by Sebastian Tennant 09 Sep '11

09 Sep '11

Hi Hans, I recently wrote the following post on the Quicklisp mailing list: http://permalink.gmane.org/gmane.lisp.quicklisp/69 and you can read Zach's reply here: http://permalink.gmane.org/gmane.lisp.quicklisp/70 Here's the final paragraph of Zach's reply, for the sake of convenience: "If the updated Ediware projects have important improvements, I would love to see new versioned releases published in some formal way. If that's not going to happen, I can look into pulling the projects from git [...]" I suspect formal release tarballs for each and every project in edicl would be quite a lot of work for you (as it probably was for Edi) so how about maintaining production-ready master branches (as in git-flow[1]) to make things as easy as possible for Zach? Seb [1] http://nvie.com/posts/a-successful-git-branching-model/ -- Emacs' AlsaPlayer - Music Without Jolts Lightweight, full-featured and mindful of your idyllic happiness. http://home.gna.org/eap

3 3

[hunchentoot-devel] Hunchentoot development is moving to github
by Hans Hübner 03 Sep '11

03 Sep '11

Hi, effective immediately, Hunchentoot development is going on in github: https://github.com/edicl/hunchentoot - The BKNR subversion repository will be closed in a while, and github will be the authoritative source for development versions. Feel free to fork, send pull requests, open issues and discuss commits. The "edicl" organization on github also has repository for several other libraries that Edi has written. No current development plans exist, but if you have enhancements to any of these libraries, pull requests are welcome. -Hans

3 3

[hunchentoot-devel] Two bugs in development head (stable version unaffected)
by Wukix Inc. 29 Aug '11

29 Aug '11

Hello All, We have become aware of what seems to be two bugs in Hunchentoot svn head (stable version is unaffected). The first one was discovered by, and should be credited to J.P. Larocque. The issue is that not only is Content-Range unnecessarily included in HTTP responses, but the upper value of the range is off by 1. For example, look at these response headers: < HTTP/1.1 200 OK < Content-Length: 14260 < Content-Range: bytes 0-14260/* J.P.'s analysis follows: =============== Content-Range appears in response, but the status code is 200 rather than 206 (Partial Content). That's odd, but not illegal as far as I can tell. But the Content-Length is definitely inconsistent with the Content-Range. HTTP 1.1 byte ranges are inclusive: The last-byte-pos value gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets start at zero. -- HTTP 1.1 14.35.1 Byte Ranges http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.35 So a range of [0,14260] indicates a length of 14261 bytes, but that's different from the Content-Length value. =============== The second issue, which was our own discovery, is that the content-type will be incorrect when serving a 304 (Not Modified) response. The content-type issue can be reproduced in Chrome/Chromium with the developer tools enabled. Basically, request some page while viewing the network tab. When you hit refresh (triggering status 304 instead of first visit 200), you will see the content type will be incorrect for images, javascript, or any other non-html. The content-type issue seems to be caused by a change to the order of operations within handle-static-file of misc.lisp. The content type needs to be set before before calling handle-if-modified-since, which could otherwise abort before the proper content type is set. Both of these issues can be fixed by reverting to an earlier version of misc.lisp. As we already mentioned, the stable version of Hunchentoot is not affected. Thanks, The Team at Wukix, Inc.

2 1

[hunchentoot-devel] Get client's time
by Matus Kmit 29 Jul '11

29 Jul '11

Hi everyone i am new to web programming and hunchentoot. i have the following question: How do one get client's time with hunchentoot? Does the http request contain this information and can one inspect on that within hunchentoot? Or what is the other way to do it? On my main page, i need to know the exact hour and minute of the client before generating the appropriate site content. Thanks Matus

2 2

[hunchentoot-devel] session-value
by Jens Teich 16 Jul '11

16 Jul '11

Trying to update a project from 0.15.6 to 1.1.1. (setf (session-value 'x) 42) throws error 'called session with unpaired keyword'. What am I missing? Jens

2 4

[hunchentoot-devel] Treten Sie meinem Netzwerk auf LinkedIn bei
by Eli Naeher über LinkedIn 13 Jul '11

13 Jul '11

LinkedIn ------------ Eli Naeher möchte Sie als Kontakt auf LinkedIn hinzufügen: ------------------------------------------ Ich möchte Sie gerne zu meinem beruflichen Netzwerk auf LinkedIn hinzufügen. Einladung von Eli Naeher annehmen http://www.linkedin.com/e/bxhy9y-gq2tbc3i-6/53mvQnCmNTJiD3hCE0Ep5J1I-StDsAz… Einladung von Eli Naeher anzeigen http://www.linkedin.com/e/bxhy9y-gq2tbc3i-6/53mvQnCmNTJiD3hCE0Ep5J1I-StDsAz… ------------------------------------------ Wussten Sie schon, dass Sie sich mit Ihrem Fachwissen auf LinkedIn profilieren können, um Stellen- bzw. Beratungsangebote zu erhalten und Ihr berufliches Ansehen zu verbessern? Beantworten Sie Fragen unter "LinkedIn Fragen & Anworten", um in der weltweiten Gemeinschaft von Fach- und Führungskräften auf sich aufmerksam zu machen. http://www.linkedin.com/e/bxhy9y-gq2tbc3i-6/abq/inv-24/ -- (c) 2011, LinkedIn Corporation

1 0

[hunchentoot-devel] Timing out when reading long post requests?
by Oleg Sivokon 07 Jul '11

07 Jul '11

Hello, I'm not sure what is causing this error (please see the stack trace below), all I can say it's relatively big XML being sent. I must be doing something tremendously inefficient or else this error means something else, but I hope you would be able to advise: [2011-07-06 14:20:27 [ERROR]] I/O timeout reading #<SB-SYS:FD-STREAM for "a socket" {B8E0AA1}>. 0: (SB-DEBUG::MAP-BACKTRACE #<CLOSURE (LAMBDA #) {B9034D5}>)[:EXTERNAL] 1: (BACKTRACE 536870911 #<SB-IMPL::STRING-OUTPUT-STREAM {B903471}>) 2: (TRIVIAL-BACKTRACE:PRINT-BACKTRACE-TO-STREAM #<SB-IMPL::STRING-OUTPUT-STREAM {B903471}>) 3: (HUNCHENTOOT::GET-BACKTRACE) 4: ((FLET #:LAMBDA284) #<SB-SYS:IO-TIMEOUT {B903139}>) 5: (SIGNAL #<SB-SYS:IO-TIMEOUT {B903139}>)[:EXTERNAL] 6: (ERROR SB-SYS:IO-TIMEOUT)[:EXTERNAL] 7: (SB-IMPL::SIGNAL-TIMEOUT SB-SYS:IO-TIMEOUT)[:EXTERNAL] 8: (SB-IMPL::REFILL-INPUT-BUFFER #<SB-SYS:FD-STREAM for "a socket" {B8E0AA1}>) 9: (SB-IMPL::FD-STREAM-READ-N-BYTES #<SB-SYS:FD-STREAM for "a socket" {B8E0AA1}> #(97 108 121 116 105 99 115 62 10 32 32 102 49 50 51 52 53 54 55 56 57 48 . . . long array of data ) 0 8191 NIL) 10: (SB-IMPL::ANSI-STREAM-READ-SEQUENCE #(97 108 121 116 105 99 115 62 10 32 32 102 49 50 51 52 53 54 55 56 57 48 . . . long array of data ) #<SB-SYS:FD-STREAM for "a socket" {B8E0AA1}> 0 8191) 11: (READ-SEQUENCE #(97 108 121 116 105 99 115 62 10 32 32 102 49 50 51 52 53 54 55 56 57 48 . . . long array of data ) #<SB-SYS:FD-STREAM for "a socket" {B8E0AA1}>)[:EXTERNAL] 12: ((SB-PCL::FAST-METHOD TRIVIAL-GRAY-STREAMS:STREAM-READ-SEQUENCE (FLEXI-STREAMS:FLEXI-INPUT-STREAM T T T)) #<unavailable argument> #<unavailable argument> #<unavailable argument> #<unavailable argument> #<unavailable argument> #<unavailable argument>)[:EXTERNAL] 13: ((LAMBDA (SB-PCL::.PV. SB-PCL::.NEXT-METHOD-CALL. SB-PCL::.ARG0. SB-PCL::.ARG1. SB-PCL::.ARG2. SB-PCL::.ARG3. SB-INT:&MORE SB-PCL::.DFUN-MORE-CONTEXT. SB-PCL::.DFUN-MORE-COUNT.)) #<unused argument> #<unused argument> #<FLEXI-STREAMS:FLEXI-IO-STREAM {B8EA781}> #(97 108 121 116 105 99 115 62 10 32 32 102 49 50 51 52 53 54 55 56 57 48 . . . long array of data ) 0 8191 -307111303 0) 14: (READ-SEQUENCE #(97 108 121 116 105 99 115 62 10 32 32 102 49 50 51 52 53 54 55 56 57 48 . . . long array of data ) #<FLEXI-STREAMS:FLEXI-IO-STREAM {B8EA781}>)[:EXTERNAL] 15: ((SB-PCL::FAST-METHOD RUNES::XSTREAM-UNDERFLOW (RUNES:XSTREAM)) #<unavailable argument> #<unavailable argument> #<RUNES:XSTREAM [main document :MAIN NIL]>) 16: (CXML::READ-NAME-TOKEN #<unavailable argument>) 17: (CXML::READ-TAG-2 #S(CXML::ZSTREAM :TOKEN-CATEGORY :SEEN-< :TOKEN-SEMANTIC NIL :INPUT-STACK (#<RUNES:XSTREAM [main document :MAIN NIL]>)) #<RUNES:XSTREAM [main document :MAIN NIL]> :STAG) 18: (CXML::FIX-SEEN-< #S(CXML::ZSTREAM :TOKEN-CATEGORY :SEEN-< :TOKEN-SEMANTIC NIL :INPUT-STACK (#<RUNES:XSTREAM [main document :MAIN NIL]>))) 19: (CXML::P/DOCUMENT #S(CXML::ZSTREAM :TOKEN-CATEGORY :SEEN-< :TOKEN-SEMANTIC NIL :INPUT-STACK (#<RUNES:XSTREAM [main document :MAIN NIL]>)) #<RUNE-DOM::DOM-BUILDER {B8EB0B9}>)[:EXTERNAL] 20: ((LAMBDA (CXML::ZSTREAM)) #S(CXML::ZSTREAM :TOKEN-CATEGORY :SEEN-< :TOKEN-SEMANTIC NIL :INPUT-STACK (#<RUNES:XSTREAM [main document :MAIN NIL]>))) 21: (CXML::CALL-WITH-ZSTREAM #<CLOSURE (LAMBDA #) {B8EE055}> #S(CXML::ZSTREAM :TOKEN-CATEGORY :SEEN-< :TOKEN-SEMANTIC NIL :INPUT-STACK (#<RUNES:XSTREAM [main document :MAIN NIL]>))) 22: (CXML::PARSE-XSTREAM #<RUNES:XSTREAM [main document :MAIN NIL]> #<RUNE-DOM::DOM-BUILDER {B8EB0B9}>)[:EXTERNAL] 23: (ROUNDS-WEB::ANALYTICS-SERVICE) ;;; This is my service I've posted the sources next 24: ((SB-PCL::FAST-METHOD HUNCHENTOOT:HANDLE-REQUEST (HUNCHENTOOT:ACCEPTOR HUNCHENTOOT:REQUEST)) #<unavailable argument> #<unavailable argument> #<HUNCHENTOOT:ACCEPTOR (host *, port 8080)> #<HUNCHENTOOT:REQUEST {B8E8A11}>) 25: ((SB-PCL::FAST-METHOD HUNCHENTOOT:PROCESS-REQUEST (T)) #<unavailable argument> #<unavailable argument> #<HUNCHENTOOT:REQUEST {B8E8A11}>) 26: ((SB-PCL::FAST-METHOD HUNCHENTOOT:PROCESS-CONNECTION (HUNCHENTOOT:ACCEPTOR T)) #<unavailable argument> #<unavailable argument> #<HUNCHENTOOT:ACCEPTOR (host *, port 8080)> #<USOCKET:STREAM-USOCKET {B8E0B31}>) 27: ((SB-PCL::FAST-METHOD HUNCHENTOOT:PROCESS-CONNECTION :AROUND (HUNCHENTOOT:ACCEPTOR T)) #<unavailable argument> #S(SB-PCL::FAST-METHOD-CALL :FUNCTION #<FUNCTION #> :PV NIL :NEXT-METHOD-CALL NIL :ARG-INFO (2)) #<HUNCHENTOOT:ACCEPTOR (host *, port 8080)> #<USOCKET:STREAM-USOCKET {B8E0B31}>) 28: ((LAMBDA ())) 29: ((FLET #:WITHOUT-INTERRUPTS-BODY-[BLOCK353]358)) 30: ((FLET SB-THREAD::WITH-MUTEX-THUNK)) 31: ((FLET #:WITHOUT-INTERRUPTS-BODY-[CALL-WITH-MUTEX]267)) 32: (SB-THREAD::CALL-WITH-MUTEX #<CLOSURE (FLET SB-THREAD::WITH-MUTEX-THUNK) {B6C77205}> #S(SB-THREAD:MUTEX :NAME "thread result lock" :%OWNER #<SB-THREAD:THREAD "Hunchentoot worker (client: 127.0.0.1:39378)" RUNNING {B8E2391}> :STATE 1) #<SB-THREAD:THREAD "Hunchentoot worker (client: 127.0.0.1:39378)" RUNNING {B8E2391}> T) 33: ((LAMBDA ())) 34: ("foreign function: #x8066E3B") 35: ("foreign function: #x8052ABD") 36: ("foreign function: #x805DC00") 37: ("foreign function: #xB7FB696E") [2011-07-06 14:20:27 [ERROR]] Error while processing connection: #<SB-SYS:FD-STREAM for "a socket" {B8E0AA1}> is closed And here's the code for that service: (in-package :rounds-web) (defun split-no-last (subject by) (loop with last = 0 for i = (position by subject :start last) if i collect (subseq subject last i) into parts and do (setf last (1+ i)) else when (> (1- (length subject)) last) collect (subseq subject last) into parts end and return parts end)) (defun time-value (raw-value) (let* ((pos (position #\. raw-value)) (result (list (subseq raw-value 0 pos))) (raw-length (length raw-value))) (if (< pos raw-length) (append result (list (subseq raw-value (1+ pos) raw-length))) result))) (defun parse-name (attribute) ;; *round*, *category* and *event-type* are hash tables defined elsewhere `(,(gethash (subseq attribute 0 1) *round*) ,(gethash (subseq attribute 1 3) *category*) ,(gethash (subseq attribute 3) *event-type*))) (defun print-attribute (stream attribute val) (format stream "Event: Round ~a | Category ~a | Type ~a~&" (first attribute) (second attribute) (third attribute)) (loop for v in val for split = (time-value v) for time = (first split) for value = (if (> (length split) 1) (second split) nil) do (format stream " Time: ~a, Value: ~a~&" time value))) (defun save-parsed-events (xml) (with-open-file (stream "./analytics.log" :direction :output :if-exists :supersede) (loop for node across (dom:child-nodes xml) do (when (eq (dom:node-type node) :element) (format stream "VideoSessionId: ~a =========================================~&" (subseq (dom:node-name node) 1)) (when (dom:attributes node) (loop with attributes = (dom:attributes node) for n from 0 upto (1- (dom:length attributes)) for attribute = (dom:item attributes n) do (print-attribute stream (parse-name (dom:name attribute)) (split-no-last (dom:get-attribute node (dom:name attribute)) #\,)))))))) (defun analytics-service () (save-parsed-events (dom:first-child (cxml:parse-stream (hunchentoot:raw-post-data :request hunchentoot:*request* :want-stream t) (cxml-dom:make-dom-builder))))) This code isn't meant for production, all it does it mocks a real service which is meant to do the same thing so I could use it for testing, yet, I'd of course like it to work :) Please, if you have anything to suggest, I'd be very happy to hear! Thanks! Oleg

4 9

[hunchentoot-devel] The question of new release
by Andrey Moskvitin 29 Jun '11

29 Jun '11

Hi, When do expect a new release of Hunchentoot? In my opinion, the HEAD version works fine. Andrey

3 2

[hunchentoot-devel] hunchentoot:*default-content-type* & hunchentoot:*hunchentoot-default-external-format*
by Thibault Langlois 15 Jun '11

15 Jun '11

*Hi, If I want to serve web pages encoded in UTF-8, I should set these two variables : (setf hunchentoot:*default-content-type* "text/html; charset=UTF-8") (setf hunchentoot:*hunchentoot-default-external-format* hunchentoot::+utf-8+) Am I correct ? Is it ok to use an internal symbol (+utf-8+) or is there another way ? Thanks, * -- Thibault Langlois FCUL / DI

3 3

[hunchentoot-devel] Invitation to connect on LinkedIn
by Andrea Massimo Chiumenti 13 Jun '11

13 Jun '11

LinkedIn ------------ General, I'd like to add you to my professional network on LinkedIn. - Andrea Massimo Andrea Massimo Chiumenti Owner at Wings Tech Milan Area, Italy Confirm that you know Andrea Massimo Chiumenti https://www.linkedin.com/e/bxhy9y-gov4ghry-11/isd/3192087151/LoQitsoO/ -- (c) 2011, LinkedIn Corporation

1 0