From: Lars Rune Nøstdal
Subject: Defacto socket compatibility layer library?
Date: 
Message-ID: <pan.2006.10.20.13.19.23.103697@gmail.com>
Hey,
Since I need to do some "scripting" I'm thinking I should use CLISP
for this instead of SBCL.

The differences between the socket-implementations seem (quick look)
somewhat negligible - but to save some time when switching back and forth
between these two (and others?), are there any already existing
compatibility layers for sockets that are "defacto" the way `CFFI' is for
FFI?

I've seen `usocket' but it seems to lack server-sockets?

-- 
Lars Rune Nøstdal
http://lars.nostdal.org/
From: Ken Tilton
Subject: Re: Defacto socket compatibility layer library?
Date: 
Message-ID: <_H5_g.19$vG3.8@newsfe10.lga>
Lars Rune Nøstdal wrote:
> Hey,
> Since I need to do some "scripting" I'm thinking I should use CLISP
> for this instead of SBCL.
> 
> The differences between the socket-implementations seem (quick look)
> somewhat negligible - but to save some time when switching back and forth
> between these two (and others?), are there any already existing
> compatibility layers for sockets that are "defacto" the way `CFFI' is for
> FFI?

LispNYC almost had something going for this Google summer of code. One 
of our number (Perry) was going to team up with someone from here on 
c.l.l to carve out a spec, and then we were thinking of taking our 
unspent mentoring fees and financing the coding by some worthy yob.

Funny you should bring this up, i was just thinking about pinging the 
parties to see if they were game for a winter project.

kt

-- 
Cells: http://common-lisp.net/project/cells/

"I'll say I'm losing my grip, and it feels terrific."
    -- Smiling husband to scowling wife, New Yorker cartoon