Oliver Bandel  <oliver@first.in-berlin.de> wrote:
+---------------
| If there are no networking-extensions to Scheme
| (I looked into the TODO-list of elk), I may write
| them, when I learned enough on scheme-programming.
+---------------

No need. Just switch to some version of Scheme that's still being
actively maintained (Elk hasn't been in quite a while). They all
have a socket library these days. [And FWIW, so do all the Common
Lisps, too.] For a Scheme with a good socket library, a thread system,
a class-based object system, and a (small but growing) library of
Web programming tools, you might want to try the DrScheme/MrEd/MzScheme
suite from Rice University <URL:http://www.cs.rice.edu/CS/PLT/>.

Specifically, see <URL:http://www.cs.rice.edu/CS/PLT/packages/doc/
mzscheme/node131.htm> for documentation of MzScheme's networking
extensions...


-Rob

p.s. If you already have some of your own extensions to Elk written
in C, they should port fairly straightforwardly to MzScheme. While
the extension interfaces *are* different, the styles are similar
enough that moving an extension library from one to the other isn't
terribly hard. (I've done it in both directions, more than once!) See
<URL:http://www.cs.rice.edu/CS/PLT/packages/doc/insidemz/index.htm>
for details on the MzScheme side.

-----
Rob Warnock, 31-2-510		rpw3@sgi.com
SGI Network Engineering		http://reality.sgi.com/rpw3/
1600 Amphitheatre Pkwy.		Phone: 650-933-1673
Mountain View, CA  94043	PP-ASEL-IA