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

[usocket-devel] [ANNOUNCE] usocket RPM available for Fedora
by Robert Uhl 23 Jun '09

23 Jun '09

I've packaged usocket for Fedora at: http://yum.octopodial-chrome.com/packages/cl-usocket Probably the easiest thing to do is to install the octopodial-chrome package and then run 'yum install cl-usocket.' -- Robert Uhl <http://public.xdi.org/=ruhl> We learn from history that we do not learn from history. --Georg Wilhelm Hegel

1 0

[usocket-devel] TIMEOUT support on SBCL
by Leslie P. Polzer 14 Jun '09

14 Jun '09

I've noticed that SBCL's SB-BSD-SOCKETS:MAKE-STREAM supports specifying a timeout but usocket declares it as unsupported. Is this simply something that needs to be changed or are there larger issue which I'm not aware of? Leslie -- http://www.linkedin.com/in/polzer

2 1

Re: [usocket-devel] [hunchentoot-devel] Socket errors during requests
by Hans Hübner 22 May '09

22 May '09

Committed to usocket trunk, thanks! On Thu, May 21, 2009 at 23:27, Andrei Stebakov <lispercat(a)gmail.com> wrote: > Hi Hans > > I did it with diff -c sbcl-before.lisp sbcl.lisp, hope that's what you > asked. > > > *** sbcl-before.lisp 2009-05-21 17:09:56.000000000 -0400 > --- sbcl.lisp 2009-05-21 16:46:55.000000000 -0400 > *************** > *** 174,179 **** > --- 174,180 ---- > . socket-type-not-supported-error) > (sb-bsd-sockets:network-unreachable-error . network-unreachable-error) > (sb-bsd-sockets:operation-timeout-error . timeout-error) > + (sb-sys:io-timeout . timeout-error) > (sb-bsd-sockets:socket-error . ,#'map-socket-error) > > ;; Nameservice errors: mapped to unknown-error > > > Thank you, > Andrei > > On Thu, May 21, 2009 at 5:11 PM, Hans Hübner <hans.huebner(a)gmail.com> wrote: >> >> On Thu, May 21, 2009 at 23:07, Andrei Stebakov <lispercat(a)gmail.com> >> wrote: >> > Yes, it works. >> > Thank you, >> >> Can you send a context diff so that I can fix usocket for everyone? >> >> Thanks, >> Hans >> >> _______________________________________________ >> tbnl-devel site list >> tbnl-devel(a)common-lisp.net >> http://common-lisp.net/mailman/listinfo/tbnl-devel > >

1 0

[usocket-devel] Create socket from file descriptor number
by Maciej Pasternacki 20 May '09

20 May '09

Hello, I am investigating possibility of running FastCGI scripts with Lisp. This is doable at least on SBCL and (recently, on trunk atm) Clozure CL, since these implementations allow for creating a socket from file descriptor as integer -- and FastCGI protocol includes the script receiving a listening socket on FD 0 (stdin), which is a pattern sometimes seen in UNIX world (e.g. inetd). To get a socket from FD, I have to resort to using unexported functions in conjunction with platform-specific calls: (usocket::make-stream-server-socket #+ccl (ccl:make-socket :address-family :internet :type :stream :connect :passive :fd 0) #+sbcl (make-instance 'sb-bsd-sockets:inet-socket :descriptor 0)) Is it possible to incorporate this usage pattern into usocket, and if yes, how should I approach preparing the patch? I was thinking along the lines of exporting MAKE-STREAM-SOCKET, MAKE-STREAM-SERVER-SOCKET, and MAKE-DATAGRAM-SOCKET functions, making them accept either an implementation-specific socket or integer file descriptor as first argument, and adding relevant backend function for creating socket by FD and element type. Would this be a correct approach, or would you suggest another API? Thanks, Maciej. -- Maciej Pasternacki -><- http://www.pasternacki.net/ -><- http://www.3ofcoins.net/

1 0

[usocket-devel] usocket on ECL 9.4.0
by Chun Tian (binghe) 04 Apr '09

04 Apr '09

Hi, ECL community I met some problems when compiling usocket on ECL 9.4.0, below is the error outputs: ============= ;;; gcc -g -O2 -fPIC -fno-common -D_THREAD_SAFE -Ddarwin -O "-I/ Users/binghe/include/" -w -c "/private/var/folders/3x/ 3xMxiHaQGSqRfjv9Z200B++++TI/-Tmp-/ECLINIThcmJG7.c" -o "/private/var/ folders/3x/3xMxiHaQGSqRfjv9Z200B++++TI/-Tmp-/ECLINIThcmJG7.o" ;;; Note: Invoking external command: Undefined symbols: "_cl_alloc_atomic", referenced from: _L2fdset_alloc in sbcl.o _L7get_host_name in sbcl.o ld: symbol(s) not found collect2: ld returned 1 exit status (SYSTEM "gcc -o \"/Volumes/User/Lisp/usocket/trunk/backend/sbcl.fas\" - L\"/Users/binghe/lib/\" \"/private/var/folders/3x/3xMxiHaQGSqRfjv9Z200B ++++TI/-Tmp-/ECLINIThcmJG7.o\" \"/Volumes/User/Lisp/usocket/trunk/ backend/sbcl.o\" -bundle -lecl -lpthread -lm ") returned non- zero value 1 ;;; gcc -o "/Volumes/User/Lisp/usocket/trunk/backend/sbcl.fas" -L"/ Users/binghe/lib/" "/private/var/folders/3x/3xMxiHaQGSqRfjv9Z200B+++ +TI/-Tmp-/ECLINIThcmJG7.o" "/Volumes/User/Lisp/usocket/trunk/backend/ sbcl.o" -bundle -lecl -lpthread -lm Broken at SI:BYTECODES.Available restarts: 1. (CONTINUE) Continues anyway. 2. (TRY-RECOMPILING) Try recompiling sbcl 3. (RETRY) Retry performing #<ASDF:COMPILE-OP NIL 29930936> on #<ASDF:CL-SOURCE-FILE "sbcl" "usocket" 29830384>. 4. (ACCEPT) Continue, treating #<ASDF:COMPILE-OP NIL 29930936> on #<ASDF:CL-SOURCE-FILE "sbcl" "usocket" 29830384> as having been successful. ============= I think following code in usocket break above build: (defun fdset-alloc () (ffi:c-inline () () :pointer-void "cl_alloc_atomic(sizeof(fd_set))" :one-liner t)) It seems that the function "cl_alloc_atomic" doesn't exist anymore. 1. What should we (usocket) do instead in ECL 9.4.0? 2. Is there anyway to detect the exist of "cl_alloc_atomic" in any ECL versions? (ECL doesn't put any version information in CL *features*, and we (usocket) want to support more ECL versions as many as possible) Regards, Chun Tian (binghe)

2 2

None
by None 13 Mar '09

13 Mar '09

1 0

[usocket-devel] Patch for ECL version 8.12
by Julian Fondren 18 Feb '09

18 Feb '09

ECL removed cl_alloc_atomic back in October, before the 8.12 release; this was then already an deprecated alias for ecl_alloc_atomic. The attached patch also gives find its required argument, and adds "*.o" to match files generated by ECL.

1 0

[usocket-devel] Unix domain sockets
by Julian Stecklina 04 Feb '09

04 Feb '09

Hello, I am currently implementing a D-BUS binding (http://github.com/blitz/cl-dbus) that needs a networking compatibility layer with support for TCP and local sockets. Not having to write implementation-dependent code to achieve this would be quite beneficial to the project. I'd like to ask, if there is any interest in integrating Unix domain sockets (AF_LOCAL) or Linux' abstract socket hack into usocket. Regards, -- Julian Stecklina Well, take it from an old hand: the only reason it would be easier to program in C is that you can't easily express complex problems in C, so you don't. - Erik Naggum (in comp.lang.lisp)

3 2

[usocket-devel] [ANNOUNCE] usocket 0.4.1
by Erik Huelsmann 07 Jan '09

07 Jan '09

On behalf of the usocket development team, I'm proud to be able to announce usocket 0.4.1: a stability release in the 0.4 series of the sockets programming portability library usocket. This release provides (small) fixes for most backends. The library is ASDF installable; the project page can be found at http://common-lisp.net/project/usocket/. Erik Huelmann

1 0

[usocket-devel] :timeout NIL for wait-for-input returns immediately on SBCL
by Chaitanya Gupta 24 Dec '08

24 Dec '08

Hi, On SBCL, providing :timeout NIL to wait-for-input returns immediately even when there is no input on any of the provided sockets (the documentation says it should wait indefinitely). Attached is a patch (svn diff) which fixes this, but I am not very sure about how sb-unix:unix-fast-select works, so its be best if someone who knows better can review it before committing this patch. :) Cheers, Chaitanya

2 2