From: lucio@proxima.alt.za
To: ericvh@gmail.com, 9fans@cse.psu.edu
Subject: Re: [9fans] webscript
Date: Fri, 7 Oct 2005 21:09:20 +0200 [thread overview]
Message-ID: <cc755e271db2cd23e6c797303b42780d@proxima.alt.za> (raw)
In-Reply-To: <a4e6962a0510070431x1235c176k5ae35fd9d9dc0c55@mail.gmail.com>
> Seems like I recall seeing an Expect derrivative that worked with
> websites - can't seem to google it now. Not sure it worked as easily
> as you are describing, but it might be a step in the right direction.
I'm in the wrong academic league, but the nearest I can envisage doing
something along these lines is tclhttpd. By Brent Welch, it has a lot
going for it.
++L
next prev parent reply other threads:[~2005-10-07 19:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 7:01 Russ Cox
2005-10-07 11:31 ` Eric Van Hensbergen
2005-10-07 19:09 ` lucio [this message]
2005-10-07 11:42 ` Dimitry Golubovsky
2005-10-08 2:03 ` Jack Johnson
2005-10-07 17:06 ` Bakul Shah
2005-10-07 18:11 ` Skip Tavakkolian
2005-10-07 20:11 ` erik quanstrom
2005-12-17 21:26 ` Caerwyn Jones
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cc755e271db2cd23e6c797303b42780d@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@cse.psu.edu \
--cc=ericvh@gmail.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 NNTP newsgroup(s).