August 2008 - drakma-devel@common-lisp.net

[drakma-devel] :close nil
by Stas Boukarev 27 Aug '08

27 Aug '08

When I call http-request with :close nil argument it takes 6 seconds more: CL-USER> (time (drakma:http-request "http://192.168.1.2/")) Evaluation took: 0.013 seconds of real time 0.008001 seconds of total run time (0.008001 user, 0.000000 system) 61.54% CPU 17,442,126 processor cycles 233,168 bytes consed "..." 200 ((:CONNECTION . "close") (:CONTENT-LENGTH . "917") (:CONTENT-TYPE . "text/html; charset=utf-8") (:DATE . "Mon, 25 Aug 2008 12:46:20 GMT") (:SERVER . "Hunchentoot 0.15.7")) #<PURI:URI http://192.168.1.2> #<FLEXI-STREAMS:FLEXI-IO-STREAM {1005E78681}> T "OK" CL-USER> (time (drakma:http-request "http://192.168.1.2/" :close nil)) Evaluation took: 6.428 seconds of real time 0.488030 seconds of total run time (0.400025 user, 0.088005 system) [ Run times consist of 0.240 seconds GC time, and 0.249 seconds non-GC time. ] 7.59% CPU 212 lambdas converted 994,309,191 processor cycles 18,388,176 bytes consed "..." 200 ((:CONTENT-LENGTH . "917") (:CONTENT-TYPE . "text/html; charset=utf-8") (:DATE . "Mon, 25 Aug 2008 12:46:04 GMT") (:SERVER . "Hunchentoot 0.15.7")) #<PURI:URI http://192.168.1.2> #<FLEXI-STREAMS:FLEXI-IO-STREAM {100799E001}> NIL "OK" Drakma and all dependancies are latest, tested with SBCL and CCL, and different web servers. -- With Best Regards, Stas.

3 10

[drakma-devel] ACL can't find WITH-CHARACTER-STREAM-SEMANTICS
by Chaitanya Gupta 21 Aug '08

21 Aug '08

Hi, When I try to call HTTP-REQUEST in ACL 8/OS X (using the dev version of DRAKMA), I get the following error/backtrace: attempt to call `DRAKMA::WITH-CHARACTER-STREAM-SEMANTICS' which is an undefined function. [Condition of type UNDEFINED-FUNCTION] Restarts: 0: [TRY-AGAIN] Try calling DRAKMA::WITH-CHARACTER-STREAM-SEMANTICS again. 1: [RETURN-VALUE] Return a value instead of calling DRAKMA::WITH-CHARACTER-STREAM-SEMANTICS. 2: [USE-VALUE] Try calling a function other than DRAKMA::WITH-CHARACTER-STREAM-SEMANTICS. 3: [STORE-VALUE] Setf the symbol-function of DRAKMA::WITH-CHARACTER-STREAM-SEMANTICS and call it again. 4: [ABORT-REQUEST] Abort handling SLIME request. 5: [ABORT] Abort entirely from this (lisp) process. Backtrace: 0: (SWANK::DEBUG-IN-EMACS #<UNDEFINED-FUNCTION @ #x108d7f42>) 1: (SWANK:SWANK-DEBUGGER-HOOK #<UNDEFINED-FUNCTION @ #x108d7f42> #<Function SWANK-DEBUGGER-HOOK>) 2: (ERROR #<UNDEFINED-FUNCTION @ #x108d7f42>) 3: (DRAKMA::WITH-CHARACTER-STREAM-SEMANTICS #(60 104 116 109 108 62 60 104 101 97 ...)) 4: ((LABELS DRAKMA:HTTP-REQUEST DRAKMA::FINISH-REQUEST) NIL) 5: (DRAKMA:HTTP-REQUEST #<PURI:URI http://www.google.co.in> :REDIRECT 4 :STREAM NIL :ADDITIONAL-HEADERS NIL) 6: ((LABELS DRAKMA:HTTP-REQUEST DRAKMA::FINISH-REQUEST) NIL) 7: (DRAKMA:HTTP-REQUEST "http://www.google.com") Couldn't locate the definition of WITH-CHARACTER-STREAM-SEMANTICS anywhere in the drakma source code. Am I missing some dependency? Chaitanya

3 5

[drakma-devel] Problem with USER-AGENT string on ACL8/OS X
by Chaitanya Gupta 19 Aug '08

19 Aug '08

Hi, These are the request headers that drakma sends when I run HTTP-REQUEST in ACL8 on OS X. GET / HTTP/1.1 Host: localhost User-Agent: #<Printer Error, obj=#x10000685: NIL is not a package>Accept: */* Connection: close The problem is that DRAKMA::USER-AGENT-STRING in this case returns a string with a tilde inside it i.e. "...~1/RELEASE_I386...". Cheers, Chaitanya

2 3

[drakma-devel] Query string construction, ALIST-TO-URL-ENCODED-STRING
by Maciej Pasternacki 19 Aug '08

19 Aug '08

Hello all, I use Drakma in my cl-openid project, and I need to construct query string on the fly. I need to pass along the URI objects with the query string, and finally I do not only call HTTP-REQUEST, but also call #'HUNCHENTOOT:REDIRECT on them, or just return those URLs as part of a message. Drakma allows to build query string only directly as part of HTTP-REQUEST, and does not make the functionality available to user. At the moment I use unexported ALIST-TO-URL-ENCODED-STRING, but I'd like to ask if there is any possibility of having ALIST-TO-URL-ENCODED-STRING and URL-ENCODE exported as part of official API? It would be certainly useful, and I think I am not the only one who needs to manipulate URIs and query strings. Regards, Maciej. -- -><- Maciej 'japhy' Pasternacki -><- http://www.pasternacki.net/ -><-

2 1