unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Alan Grover <awgrover@mail.msen.com>
Subject: mod_lisp for guile
Date: Thu, 15 Sep 2005 13:25:10 -0400	[thread overview]
Message-ID: <4329AE76.4000606@mail.msen.com> (raw)

Inspired by Guillaume  Germain on the comp.lang.scheme group, I wrote a
mod_lisp implementation for Guile. Find it at:
https://sourceforge.net/project/showfiles.php?group_id=141512&package_id=163742

I only implemented the mod_lisp protocol, leaving query-string/POST and
HTML utilities for an external package (for example, TTN's www-guile). I
did give in to weakness and provide an optional ability to create a
thread for each request (did you know that "accept" blocks all threads?
Yum.).

It is minimally tested (it has an internal test daemon).

I'd appreciate some feedback:
* Will you use it?
* Should I remove the thread-creation stuff and stick simply to mod_lisp
protocol?
* Should I provide an interface to integrate with TTN's www-guile?
* How bad is the user-interface?
* What do you think of providing a lazy-list of requests, rather than
the current technique of passing control to a blocking-looping-function?
* Do you want to see a SRFI that provides _just_ the mod_lisp protocol?



_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user


             reply	other threads:[~2005-09-15 17:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-15 17:25 Alan Grover [this message]
2005-09-16 18:46 ` mod_lisp for guile Neil Jerram
2005-09-19 14:46   ` Alan Grover
2005-09-19 21:32     ` Neil Jerram
2005-09-20  3:24       ` Alan Grover
2005-09-20  4:44         ` Threads (was: mod_lisp for guile) Tomas Zerolo
2005-09-20 12:12           ` Threads Alan Grover
2005-12-04 10:07         ` mod_lisp for guile Neil Jerram
2005-12-05 17:21           ` Alan Grover
2005-12-15 23:21             ` Neil Jerram
2005-12-16 13:21               ` Alan Grover
2005-12-29 10:18                 ` Neil Jerram

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=4329AE76.4000606@mail.msen.com \
    --to=awgrover@mail.msen.com \
    /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).