unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Sebastian Tennant <sebyte@smolny.plus.com>
To: guile-user@gnu.org
Subject: Re: Uploading Word documents, PDFs, PNG files etc
Date: Tue, 12 May 2009 10:15:52 +0000	[thread overview]
Message-ID: <7i0m1vaf.fsf@vps203.linuxvps.org> (raw)
In-Reply-To: 87vdo7au56.fsf@ambire.localdomain

Quoth Thien-Thi Nguyen <ttn@gnuvola.org>:
> () Sebastian Tennant <sebyte@smolny.plus.com>
> () Sun, 10 May 2009 16:21:29 +0000
>
>       (with-output-to-file (string-append USER-UPLOAD-DIR upload-fname)
>         (lambda ()
>           (display upload)))
>
> Perhaps you can convert the string in variable `upload' to a uniform vector
> and write it out using `uniform-vector-write'.  It may be the case, too,
> that the string can be passed to `uniform-vector-write' directly, e.g.:
>
>       (with-output-to-file (string-append USER-UPLOAD-DIR upload-fname)
>         (lambda ()
>           (uniform-vector-write upload)))

Nope.

On closer inspection, it is the call to (cgi:upload ...) which throws
the error so there is no way of converting the result to a vector before
trying to write it to disk.

 cgi.scm:

 (define (upload name)
   (and=> (uploads name) car))

cgi.scm is so full of closures it makes my head swim but from what I can
gather the upload is extracted and stored in memory at the
initialisation stage (cgi:init) which would suggest to me that the
problem doesn't lie within the procedure parse-form-multipart as this is
called by (cgi:init).

Given that guile 1.8.6 can actually handle null chars in strings
(despite what the error message says) what could the problem be?

Seb

P.S. Documentation bug - the procedure 'and=>' is missing from the
     manual.  What's the difference between the way the upload procedure
     is written above and simply:

      (define (upload name)
        (car (uploads name)))

-- 
Emacs' AlsaPlayer - Music Without Jolts
Lightweight, full-featured and mindful of your idyllic happiness.
http://home.gna.org/eap





  reply	other threads:[~2009-05-12 10:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-10 16:21 Uploading Word documents, PDFs, PNG files etc Sebastian Tennant
2009-05-11 15:11 ` Ludovic Courtès
2009-05-11 15:55   ` Thien-Thi Nguyen
2009-05-11 23:17     ` Ludovic Courtès
2009-05-12  3:15 ` Thien-Thi Nguyen
2009-05-12 10:15   ` Sebastian Tennant [this message]
2009-05-12 10:33     ` Ludovic Courtès
2009-05-12 11:16       ` Sebastian Tennant
2009-05-13 14:02   ` Sebastian Tennant
2009-05-13 15:02     ` Ludovic Courtès
2009-05-13 18:01       ` Sebastian Tennant
2009-05-13 19:09       ` Sebastian Tennant
2009-05-13 19:23         ` Linas Vepstas
2009-05-14  3:47           ` Keith Wright
2009-05-14 12:49             ` Sebastian Tennant
2009-05-14 13:13               ` Sebastian Tennant
2009-05-17 21:55               ` Ludovic Courtès
2009-05-19  4:48                 ` Sebastian Tennant
2009-05-19  4:59                   ` Sebastian Tennant
2009-05-19  7:50                   ` Ludovic Courtès
2009-05-21  5:22                     ` Sebastian Tennant
2009-05-21 10:47                       ` Thien-Thi Nguyen

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=7i0m1vaf.fsf@vps203.linuxvps.org \
    --to=sebyte@smolny.plus.com \
    --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).