January 2010 - drakma-devel@common-lisp.net

[drakma-devel] Patch - Accept-Encoding: gzip
by Red Daly 05 Feb '10

05 Feb '10

Dear drakma users, I made drakma accept gzipped message bodies by default, and also automatically decode them. A patch is attached. Unfortunately this adds a new dependency on gzip-sequence (which in turn depends on salza2). See the docstrings for more details. To sum it up: if WANT-STREAM is T, It wraps the returned stream in a flexi-stream that wraps a gzip-input-stream. Otherwise, it decodes the sequence before returning from HTTP-REQUEST. Thanks, Red

2 3

[drakma-devel] Drakma doesn't work on CLISP because of unsupported TCP_NODELAY
by Anton Vodonosov 21 Jan '10

21 Jan '10

Hello, The recent Drakma (1.1.0) doesn't work on CLISP because of :NODELAY T passed to USOCKET:SOCKET-CONNECT. :NODELAY is not supported on CLISP and usocket signals an error. IMHO it would be better to remove the :NODELAY T, not only because of the CLISP support, but also because the Nagle's algorithm disabled by :NODELAY T seems to be a feature rather than a problem. Best regards, - Anton

1 0

[drakma-devel] post requests and content-type
by Adam Dodek Michalik 08 Jan '10

08 Jan '10

Hey, I noticed that when using POST method, Drakma completely ignores content-type provided by user. That's kinda bad for me, since I'd like to be able to send the content's charset as well - so that Content-Type header looks for instance like this: application/x-www-form-urlencoded; charset=utf-8 Modifying drakma so that it uses content-type provided by user is trivial, but maybe there are other reasons behind this behaviour I'm not aware of. -- Adam Michalik vel Dodek Dodecki <dodek(a)dodecki.net>

1 0

[drakma-devel] Drakma - problem with http-request on SBCL 1.0.34
by Fred Gibson 07 Jan '10

07 Jan '10

I've found a small problem in Drakma's http-request where in a call to usocket:socket-connect it sent the key :nodelay which doesn't exist for sbcl's socket connect version, so I changed that call in drakma to this: (usocket:socket-stream (usocket:socket-connect host port :element-type 'octet #+:openmcl :deadline #+:openmcl deadline #-:sbcl :nodelay #-:sbcl t)) Then it seemed to work just fine. My best, Fred Gibson Founder / Software Developer http://www.streamfocus.com (c)2010 Organon Technologies LLC

3 5