The following message is a courtesy copy of an article
that has been posted to gmane.lisp.scheme.scsh.devel,gmane.lisp.scheme.scsh as
This in fact a followup on my earlier mail.
I've now diverged from earlier plan to go the route outlined by Mike
Sperber (clean up the scsh networking API, then implement that on
Scheme 48), but instead started from Taylor campells TCP interface
proposal, generalized it a bit, so it can also cover
stream-oriented connections in other domains (e.g. AF_UNIX) and added
datagram (specifically UDP) support -- see  for the resulting
(still very rough) proposal. If have now started implementing this for
Scheme 48; at the bottom of the mail is a short note on the current
status and some implementation details.
I think this network API is general enough in principle that it could
be submitted as an SRFI when polished and specified better. In
comparison to the scsh (highlevel) API, I think it abstracts a bit
better from the underlying BSD socket API; I'd really appreciate
comments from the users of the current networking API of scsh
(esp. SUnet developers) and Scheme 48, if
1) my proposal would suffice the needs of SUnet, if not, what else
would be needed
2) you think this proposal is viable (if brushed up appropriatly)
as a high-level, common network API for Scheme 48 and scsh
If 2) can be agreed upon, I'd volunteer implementing the proposal on
top of the current scsh interface, which should be quite easy, and
give porting SUnet to it a go.
Also, I'd like to know about what the state of things
wrt. coordinating the network API with the PLT people (that Mike
Andreas Rottmann | Rotty@ICQ | 118634484@ICQ | email@example.com
http://yi.org/rotty | GnuPG Key: http://yi.org/rotty/gpg.asc
Fingerprint | DFB4 4EB4 78A4 5EEE 6219 F228 F92F CFC5 01FD 5B62
Python is executable pseudocode, Perl is executable line-noise.