From: Amirouche <amirouche@hypermove.net>
To: guile-user@gnu.org
Subject: Re: Using fibers in guile-websocket
Date: Sun, 23 Apr 2017 12:38:55 +0200 [thread overview]
Message-ID: <c6f8e671-12a4-c033-75ca-d3a91a14c0fd@hypermove.net> (raw)
In-Reply-To: <273a434f-571d-16b9-e0da-4a6a35e27132@hypermove.net>
Le 16/04/2017 à 17:57, Amirouche a écrit :
> Hi all
>
> I am trying to run guile-websocket with fibers, but I failed. I pushed
> the code online:
>
> git clone https://github.com/amirouche/guile-websocket
>
> It seems to me the code blocks when trying to read something on the
> socket. To reproduce
> configure the project using the autotools and then fire the test.scm
> with the following
> command:
>
> ./pre-inst-env guile test.scm
>
> and open the test.html in a browser. This should print a "connected"
> message in the web
> console and "hello there". But it doesn't. If you refresh the page a
> few time (7 times
> on my side) the server part completely hangs and doesn't accept new
> connections.
>
> Any help, will be greatly appreciated.
>
>
> Amirouche ~ amz3
>
Anyone?
prev parent reply other threads:[~2017-04-23 10:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-16 15:57 Using fibers in guile-websocket Amirouche
2017-04-23 10:38 ` Amirouche [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=c6f8e671-12a4-c033-75ca-d3a91a14c0fd@hypermove.net \
--to=amirouche@hypermove.net \
--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).