usocket-devel

usocket-devel@common-lisp.net

248 discussions

[usocket-devel] ECL and MSVC
by Seth Burleigh 27 Dec '09

27 Dec '09

When using ecl that has been built with msvc, the code in sbcl.lisp #-:wsock (ffi:clines "#include <errno.h>" "#include <sys/socket.h>") #+:wsock (ffi:clines "#ifndef FD_SETSIZE" "#define FD_SETSIZE 1024" "#endif" "#include <winsock2.h>") (ffi:clines "#include <sys/time.h>" "#include <ecl/ecl-inl.h>" ) Doesn't build because sys/time is not available in msvc. What header should I include instead?

1 0

[usocket-devel] wait-for-input's ready-only argument
by Mihai Bazon 18 Dec '09

18 Dec '09

Hi folks, What's with the ready-only arg to wait-for-input? It's not documented anywhere, but I noticed that if I don't pass T for it my code behaves strangely. Cheers, -Mihai

2 2

[usocket-devel] [discuss] usocket direction
by Chun Tian (binghe) 08 Dec '09

08 Dec '09

Hi, I'm "disappeared" for several months from public CL community, because I'm hired by Gensym for improving their big lisp products. Now I'm partly back and still want to do contributions to usocket & other projects. For usocket project, it's long since the last release. Before next release, I personal am thinking of following plans: 1) Finish the experimental-udp branch, by cleaning some code first (reliable UDP), then finish port on CLISP & ABCL, finally merged back to trunk. 2) Add support for MCL (Macintosh Common Lisp), because the new Rosetta based MCL is alive again to Mac Lispers. 3) Add some unit test code, I'll start the first part above from not later then next month (Jan 2010), help from ABCL & CLISP users are welcome. More ideas or suggestions are also welcome, especially notes from Erik & Hans. Regards, Chun Tian (binghe)

1 0

[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

[usocket-devel] invalid initarg error
by Patrick May 16 Sep '09

16 Sep '09

I'm running the latest version of Hunchentoot available from bknr.net in Clozure CL on a 64-bit Linux box. I see this error in the logs occasionally: [2009-09-15 19:44:49 [ERROR]] Error while processing connection: :REAL- ERROR is an invalid initarg to INITIALIZE-INSTANCE for #<STANDARD- CLASS USOCKET:TIMEOUT-ERROR>. Valid initargs: (:SOCKET). From poking around in the source it appears that this is only called in the usocket package. The site doesn't appear affected. Is this a known issue? Thanks, Patrick

1 0

[usocket-devel] socket-listen and socket-accept
by Shawn Betts 09 Aug '09

09 Aug '09

Hi usocket people! First, what a great library! Easy to understand and use. However... How does one poll a server socket created with socket-listen to see if there's an incoming connection? I want to run socket-accept in that case but I can't block because my program is busy doing other stuff. I've tried wait-for-input but it always returns the server socket (lispworks & sbcl) despite there not being any pending connection. -Shawn

2 1

Re: [usocket-devel] Usocket ECL patch
by Chun Tian (binghe) 22 Jul '09

22 Jul '09

Hi, Marko Thanks, your patch is reasonable. I believe ECL doesn't have SB-SYS package. Commited as r498. Regards, Chun Tian (binghe) On 2009-7-22, 23:09, Marko Kocić wrote： > Latest usocket svn fails to complile with ECL. > Here's the quick fix. > > Regards, > Marko > <ecl.patch>

1 0

← Newer
1
...
11
12
13
14
15
16
17
...
25
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

usocket-devel