From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: guile-sources@gnu.org
Cc: guile-user@gnu.org
Subject: Guile-WWW 2.25 available
Date: Thu, 28 May 2009 16:19:15 +0200 [thread overview]
Message-ID: <87r5y99uos.fsf@ambire.localdomain> (raw)
release notes:
Standard bugfix + internal-mining + doc-detailing release.
thi
README excerpt:
This is the Guile WWW library, a set of Guile Scheme
modules to facilitate HTTP, URL and CGI programming.
NEWS excerpt:
- 2.25 | 2009-05-28
- changes to (www cgi)
- bugfix: parse cookies using comma as inter-cookie delim
- bugfix: query-string no longer masks form-data
- new proc: cgi:cookie-names
- new support for ‘uploads-lazy’ (file contents management) style
- new module: (www server-utils form-2-form)
- new (www server-utils cookies) proc: simple-parse-cookies
- new (www server-utils parse-request) procs
- hqf<-upath
- alist<-query
- read-body
- documentation spiffed
- distribution includes guile-www.pdf
- maintenance uses GNU Autoconf 2.63, GNU Automake 1.11
tarball, prettified source, etc, in dir:
http://www.gnuvola.org/software/guile-www/
atom feed:
http://www.gnuvola.org/NEWS.atom
reply other threads:[~2009-05-28 14:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r5y99uos.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=guile-sources@gnu.org \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).