Hi, Ian; 2012/5/7 Ian Price <ianpric...@googlemail.com> > > Thanks for pointing this out, and if you have other comments on the > implementation (and the close-port issue), I'll be happy to have them.
I don't understand the "close-port issue" exactly so this might be nonsense. I think you mean comment-out-ed (close-port port) of close in make-chunked-input-port. http-get in client.scm calls close-port when keep-alive? keyword be false value. http-post of Greg Benison's use keep-alive? keyword only when making headers and does not call close-port; this is why my cc-ing to Greg. In this today morning, I had thought what points need to patch if being https support. I had no experience to making that kind of codes and can't imagine I myself write it, so just a thought. open-socket-for-uri need to make a session using gnu-tls; it does handshake with a server and so on. http-get (and http-post) need to send bye to that session when keep-alive? keyword be false value. So, close-port might be a role of http-get?
