May 2010 - usocket-devel - mailman3.common-lisp.net

[usocket-devel] How to portably setsockopt
by Elliott Slaughter 20 Jul '10

20 Jul '10

Hi, I need to set SO_BROADCAST in order to enable sending packets to a broadcast address in my application. In SBCL, for example, this can be accomplished with (setf (sb-bsd-sockets:sockopt-broadcast (usocket::socket *socket*)) t) I am wondering if usocket provides any way of accomplishing this, and if this is considered inside the scope of usocket. Thanks. -- Elliott Slaughter "Don't worry about what anybody else is going to do. The best way to predict the future is to invent it." - Alan Kay

2 1

[usocket-devel] Problem with :ready-only
by Daniel Weinreb 29 Jun '10

29 Jun '10

Hi. I just tried out the latest usocket. It's not working properly for me, because wait-for-input returns true even when there isn't any input. If I change the default value of the :ready-only argument to wait-for-input to t instead of nil, that fixes the problem. I don't even understand why this argument exists; no caller seems to pass it at all! What's going on here? Thanks. -- Dan

2 5

[usocket-devel] [Patch]: Clisp can't find gethostname on Linux
by Stas Boukarev 28 Jun '10

28 Jun '10

I attached a patch which allows Clisp to find gethostname on Linux. -- With Best Regards, Stas.

2 1

[usocket-devel] wait-for-input does not work
by Daniel Weinreb 04 May '10

04 May '10

Hi. I just tried out the latest usocket, and found that wait-for-input does not work properly. To fix it, I changed the default value of the :read-only parameter from nil to t. What's going on with the :read-only parameter? No function in usocket passes this argument to wait-for-input. Thanks. -- Dan

1 0