unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: guile-user@gnu.org
Subject: Re: Guile web server example serving static files
Date: Sat, 19 Sep 2020 12:57:41 +0200	[thread overview]
Message-ID: <00a007fc-cb54-b7ce-548c-69b117a14a91@posteo.de> (raw)
In-Reply-To: <87ft7fttkh.fsf@web.de>

Hello Arne!

Thanks for the link. So far I have only tried with a tiny CSS file, so I
have no idea, whether I would run into a problem, besides memory
consumption, for big files. I wonder, whether I should simply use
sendfile described in
https://www.gnu.org/software/guile/manual/html_node/File-System.html#File-System.
I think it was mentioned to be in GUIX somewhere, as an example. So far
I did not get to look at it.

Regard,
Zelphir

On 18.09.20 09:47, Dr. Arne Babenhauserheide wrote:
> Hi Zelphir,
>
> I see that you’re getting the full file as bytevector 
>
> Zelphir Kaltstahl <zelphirkaltstahl@posteo.de> writes:
>> https://notabug.org/ZelphirKaltstahl/guile-examples/src/65ba7cead2983f1ceb8aa2d4eedfe37734e5ca56/web-development/example-03-serve-static-assets
> I see that you’re getting the full file as bytevector in response-utils.
> When I tested this in wispserve with multi-gigabyte files, I got
> gc-errors.
>
> I do string-conversion, though, because I got into problems with just
> putting a bytevector — does avoiding that avoid the problem?
>
> https://hg.sr.ht/~arnebab/wispserve/browse/wispserve/serve.w?rev=4541f36df0b0#L411
>
> Best wishes,
> Arne

-- 
repositories: https://notabug.org/ZelphirKaltstahl





      reply	other threads:[~2020-09-19 10:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-17 21:45 Guile web server example serving static files Zelphir Kaltstahl
2020-09-18  5:56 ` divoplade
2020-09-19 10:39   ` Zelphir Kaltstahl
2020-09-20  7:48   ` tomas
2020-09-20  7:52     ` divoplade
2020-09-20  8:29       ` tomas
2020-09-20  8:54         ` divoplade
2020-09-20  9:07           ` tomas
2020-09-18  7:47 ` Dr. Arne Babenhauserheide
2020-09-19 10:57   ` Zelphir Kaltstahl [this message]

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=00a007fc-cb54-b7ce-548c-69b117a14a91@posteo.de \
    --to=zelphirkaltstahl@posteo.de \
    --cc=arne_bab@web.de \
    --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).