Re: Sockets support...

[Sam S. <sd...@gn...>]

> * Douglas Philips <qtbh@znp.pbz> [2004-02-09 09:20:46 -0500]:
>
> Is there any interest in enhancing the networking facilities
> (currently in socket.d, maybe other places, I haven't chased all the
> threads down yet)? I was surprised to find (cause I just went looking)
> only support for TCP, and that is rather oddly done. For example, on
> the non-windows code, the listen call has hardwired '1' for its second
> parameter.

There have been a discussion about UDP sockets here before.
I think (although I am not sure) that someone knowledgeable explained
that UDP sockets are asynchronous and thus cannot be a basis for a Lisp
STREAM object.
There was also an opinion expressed here that "UDP is a niche need and
does not have to be in the core".

I suggest that you work out an API for UDP sockets and implement it as
a module (using FFI or not, your choice).  This will solve your
immediate need.

> I did a quick build on Panther over the weekend, but the FFI code's
> tests crashed in the configuration phase, so FFI is not yet a viable
> option, but I assume that will be fixed eventually.

I think that the current CVS FFCALL has full support for OSX.
please build from the CVS HEAD sources.

> I am still on the hook to track down the type.lisp 'caching bug'.

yeah, that would be nice.

-- 
Sam Steingold (http://www.podval.org/~sds) running w2k
<http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/>
<http://www.mideasttruth.com/> <http://www.honestreporting.com>
Lisp: its not just for geniuses anymore.