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

[drakma-devel] Sending content without loading it all in memory?
by Zach Beane 28 Oct '08

28 Oct '08

Is there any way to send a non-chunked request without having the entire content in memory at once? I'm working on an Amazon S3 client based on Drakma, but sometimes I want to upload (via PUT) very large files and I'd prefer to determine the content-length via FILE-LENGTH and upload the body buffer-by-buffer instead of all at once. Zach

3 6

[drakma-devel] Returning server protocol as the eighth value of HTTP-REQUEST
by Chaitanya Gupta 28 Oct '08

28 Oct '08

Hi, I have made a small change to HTTP-REQUEST wherein it returns the server protocol (as a keyword) as its eighth value. If its worth incorporating this change in the main drakma code, should I send a patch against the dev version (bknr svn) or the released version (0.11.5)? Cheers, Chaitanya

1 0

[drakma-devel] How to handle persistent sessions across http-request calls?
by Matthew Lamari 26 Oct '08

26 Oct '08

I acknowledge that I may be doing this wrong. I have a very trivial hunchentoot server which merely returns a string containing the Hunchentoot SessionID. >From browsers, this works - subsequent requests do not result in a new session being created. However, even (mis?) using the cookie-jar, I end up with new sessions being created. (let ((jar (make-instance 'cookie-jar))) (labels ((doit () (print (multiple-value-list (http-request http://mysite.com/:cookie-jar jar))) (print (cookie-jar-cookies jar)))) (doit) (doit) (doit) (cookie-jar-cookies jar))) The cookie seems to be replaced with each call, with a new session's cookie. I imagine hunchentoot uses cookies to track sessions - is the old cookie not being sent back? Is there something I am doing wrong? Is there a way to use Drakma to track a persistent session? The set-cookie comes back as hunchentoot-session=xx%yyy - where xx is the session number. Thanks, Matt.

1 1