usocket-devel October 2009

usocket-devel@common-lisp.net

4 participants
4 discussions

[usocket-devel] XCVB patch for usocket
by Faré 23 Oct '09

23 Oct '09

Can you apply this patch to let usocket be built by XCVB? [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Every technique is first developed, then used, important, obsolete, normalized, and finally understood.

1 0

[usocket-devel] Passnig data between ACL and ABCL Lisp processes via usockets
by Ben Olasov 18 Oct '09

18 Oct '09

I've installed the usocket code for both ACL and ABCL and have tried every permutation I can think of, but so far haven't been able to send data between Lisp processes through a two way socket stream. Yes, it sounds trivial, I know, but has anyone actually done this and, if so, could they please offer a suggestion or two as how it's done? Thanks, Ben

2 1

Re: [usocket-devel] [Ecls-list] ECL problem
by Chun Tian 18 Oct '09

18 Oct '09

Hi, Juanjo Thanks for taking my patch. I spent a little more time on checking ECL's "contrib/sockets/sockets.lisp", and it seems that things are not that serious as my first view. Only two buggy sockopt related functions are found: [Bug Description] * GET-SOCKOPT-BOOL returns wrong value (always T or throw a error) I've explained the reason (variable of actual value is dropped). * SET-SOCKOPT-BOOL returns wrong value (always T or throw a error) I believe this is a typo. [Affected public interfaces] SOCKOPT-REUSE-ADDRESS, SOCKOPT-KEEP-ALIVE, SOCKET-DONT-ROUTE, SOCKET- LINGER, SOCKOPT-REUSE-PORT and SOCKOPT-TCP-NODELAY. (Package SB-BSD- SOCKETS) [Solution] I've made a new, small patch (as in attach) to "sockets.lisp" which fixed all above issues and now ECL behaves exactly the same as SBCL when accessing above socket options: > (setq socket (make-instance 'sb-bsd-sockets:inet- socket :type :stream :protocol :tcp)) #<SB-BSD-SOCKETS:INET-SOCKET descriptor 3 4320793344> > (sb-bsd-sockets::sockopt-tcp-nodelay socket) NIL > (setf (sb-bsd-sockets::sockopt-tcp-nodelay socket) t) T > (sb-bsd-sockets::sockopt-tcp-nodelay socket) T For the original bug which Leslie P. Polzer report to USOCKET project, it's also fixed without touching USOCKET source code (if this new patch applied), I believe. Regards, Chun Tian (binghe) 在 2009-10-18，1:58， Juan Jose Garcia-Ripoll 写道： > 2009/10/17 Chun Tian <binghe.lisp(a)gmail.com>: >> For a summary, I'll suggest Juanjo merge my version first (or >> Mattew's >> version with the number "6" replaced to "IPPROTO_TCP"). I'll see >> how far I >> can go from now on. >> > > Thanks a lot for your help in debugging this and the other problems! > > I have just committed your patch --it also has the advantage that the > level is explicit, just like in SBCL's code---. It is available in > both the GIT and CVS repositories. > > Juanjo > > -- > Instituto de Física Fundamental, CSIC > c/ Serrano, 113b, Madrid 28006 (Spain) > http://juanjose.garciaripoll.googlepages.com

3 2

[usocket-devel] ECL problem
by Leslie P. Polzer 16 Oct '09

16 Oct '09

On ECL 9.10.2 I get "setsockopt: permission denied" unless I comment out this bit in backend/sbcl.lisp: ;; binghe: use SOCKOPT-TCP-NODELAY as internal symbol ;; to pass compilation on ECL without it. (when (and nodelay-specified sockopt-tcp-nodelay-p) (setf (sb-bsd-sockets::sockopt-tcp-nodelay socket) nodelay)) Looks like this kludge doesn't work anymore... Leslie -- http://www.linkedin.com/in/polzer

2 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

usocket-devel October 2009