usocket

usocket copied to clipboard

usocket 0.8.4 is broken on windows version 0.8.3 does compile

3

usocket 0.8.4 is broken on windows version 0.8.3 does compile ; caught ERROR: ; READ error during COMPILE-FILE: ; ; Symbol "BROKEN-PIPE" not found in the SB-INT package. ; ;...

etaoinbe

multicast support

1

Any possibility of adding multicast support? I'd prefer not having to use another socket library for upnp and service discovery. I know it's at least possible on sbcl since I've...

JMC-design

socketpair-like function

2

It would be nice to have a usocket API function that behaves like [`socketpair(2)`](https://man7.org/linux/man-pages/man2/socketpair.2.html). In the BSD sockets API, this function creates a pair of connected sockets. There would be...

fjl

I/O timeouts

8

I am wondering if it would be possible for usocket to support I/O timeouts on implementations that support it? This would really add a lot of value to me. I...

eugeneia

Produced documentation with HELP

3

Hi I wanted to use USOCKET for a little side project of mine and I got sidetracked into looking at its documentation. I ended up using USOCKET as a testbed...

marcoxa

unresolved external symbol 'gettimeofday' (msvc ECL, Windows 10)

4

Trying to load usocket on Windows using ECL built with MSVC throws the following error: ``` sbcl.obj : error LNK2019: unresolved external symbol gettimeofday referenced in function L10read_select C:\Users\USER\Documents\ecl\msvc\package\quicklisp\dists\quicklisp\software\usocket-0.8.3\backend\sbcl-tmpQ0855BGK.fas :...

compufox

Missing USOCKET::FDSET-ALLOC on CL REPL (EQL5, Andoid)

11

I'm trying to use hunchentoot. Before loading hunchentoot, \*FEATURES\* includes :ECL, :ECL-BYTECMP, :EQL, :EQL5 and :ANDROID -to narrow the field for you, though among these I'm aware that usocket system...

silent-entertainment

Don't default to IPv4 if the host has no IPv4 interface

4

If usocket is used on an IPv6-only host, and if the endpoint it is trying to reach resolves to both an IPv4 and IPv6 DNS address, usocket will always try...

ckonstanski

LispWorks specific: socket-accept should check is actually got a socket

1

**socket-accept** for **stream-server-usocket** in backend/lispworks.lisp needs to check that the socket it got from **comm::accept-connection-to-socket** or **comm::get-fd-from-socket** is not NIL, because both of these can return NIL for failures. What...

Yehouda

LispWorks specific: socket-shutdown on stream-usocket need to pass the stream to comm:socket-stream-shutdown (rather than the socket)

2

in backend/lispworks.lisp, the method socket-shutdown on stream-usocket currently calls comm:socket-stream-shutdown on the socket, which is wrrong, because comm:socket-stream-shutdown expects a socket-stream. It needs to pass the stream, that is replace...

Yehouda