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

Unix domain (IPC) sockets implementation
by Marcin Moskal 18 Aug '16

18 Aug '16

As far as I know usocket does not provide implementation of Unix domain sockets, nonetheless SBCL[1], CCL[2] and ECL[3] (and maybe other) implement them. After doing some research I see that feature in usocket is desired (see: usocket-devel question[4], another usocket-devel question[5]), even partially implemented[6] by @tmccombs. I would like to try to implement this feature without breaking the current API. It could be done by assuming that the ``host'' parameter in socket-connect function takes pathname -- indicating we mean the *Unix* kind of socket. In this particular case we will ignore the ``port'' portion(or signal condition when it is not ``nil''). I am looking for comments and advice. [1] http://www.sbcl.org/manual/#Local-_0028Unix_0029-Domain-Sockets [2] http://ccl.clozure.com/manual/chapter8.1.html [3] https://gitlab.com/embeddable-common-lisp/ecl/blob/develop/contrib/sockets/… [4] https://mailman.common-lisp.net/pipermail/usocket-devel/2008-August/000198.… [5] https://mailman.common-lisp.net/pipermail/usocket-devel/2009-February/00025… [6] https://github.com/usocket/usocket/compare/master...tmccombs:unix-sockets -- Regards, Marcin Moskal

4 3

[ANN] usocket 0.6.4
by Chun Tian 19 Mar '16

19 Mar '16

Dear Lispers, We’re glad to announce usocket 0.6.4. Changes in this release: * New feature: [SBCL] IPv6 support (patch from Guillaume LE VAILLANT, #15) * New feature: [API] SOCKET-SHUTDOWN added (patch from Thayne McCombs #9) * New feature: [Corman] minimal initial support of this platform * Bugfix: [SBCL/win32] wait-for-input nil-timeout bug (patch from Michal Herda, #13) * Bugfix: [ECL] included unistd.h for gethostname() (patch from Daniel Kochmanski, #7) * Bugfix: [LispWorks] SOCKET-RECEIVE now updates %READ-P (patch from Frank James) Special thanks to Guillaume LE VAILLANT [1] for his patch on improved IPv6 support of SBCL. As usual, if you want to download this release, please check http://common-lisp.net/project/usocket/releases/ or just wait for next Quicklisp monthly dist updates. The API documentation page was here: http://common-lisp.net/project/usocket/api-docs.shtml Any feedback - bugs or hugs - is greatly appreciated. Anyone is welcome to send pull request to our Git [1]: https://github.com/usocket/usocket.git Regards, Chun Tian (binghe) usocket team [1] https://github.com/glv2

2 1

[webpage][deadlink][ECL]
by Daniel Kochmański 17 Mar '16

17 Mar '16

Hey, I'm not sure if it's the correct place to report it, but the link on the webpage (https://common-lisp.net/project/usocket/) to ECL (under "supported imlementations") points at sourceforge (which redirects to the correct url) – anyway, the correct address is: https://common-lisp.net/project/ecl/ Thanks! Regards, Daniel -- Daniel Kochmański | Poznań, Poland ;; aka jackdaniel "Be the change that you wish to see in the world." - Mahatma Gandhi

2 1

Strange error when calling wait-for-input in clisp
by Blah Blahh 06 Dec '15

06 Dec '15

This line (usocket:wait-for-input some-client-socket :timeout 0 :ready-only t) Causes a condition "CDR: :INPUT is not a list." It occurs regardless of whether some-client-socket is in a list or not. The same issue doesn't happen when working with a socket returned by socket-listen, only when some-client-socket is a socket created by socket-connect or socket-accept. Backtrace here: http://pastebin.com/zjT8ghDA If anyone finds a relatively simple fix, but it would take a while to get it updated in quicklisp, a response would be appreciated. Thanks for the library! - Reepca

1 0

Shutdown socket-server
by Patrick May 12 Nov '15

12 Nov '15

How do I cleanly shutdown a running socket-server? Thanks, Patrick

1 0

Re: SOCKET-SERVER missing docs?
by Chun Tian (binghe) 27 Sep '15

27 Sep '15

Well, I guess the job is to move some documents from web page into the source code. I’ll do it in next release. Thanks. Chun > Il giorno 25/set/2015, alle ore 16:24, Andreas Davour <ante(a)Update.UU.SE> ha scritto: > > > Hi > > I just went back to usocket after a long time away, and realized when I typed C-d d in the wrong place in SLIME that SOCKET-SERVER seems to be lacking documentation, even though there's a bunch at: > https://common-lisp.net/project/usocket/api-docs.shtml > > Maybe that is an oversight, or is it intentional? > > -andreas > > -- > "economics is a pseudoscience; the astrology of our time" > Kim Stanley Robinson >

1 0

usocket:with-mapped-conditions documentation
by Mark H. David 24 Aug '15

24 Aug '15

Is there any documentation for: usocket:with-mapped-conditions I could not find any. Also, would like to know if there's doc for usocket conditions. Thanks, Mark

2 1

CCL vector quad host problems
by Sebastian Christ 20 Jul '15

20 Jul '15

Hi list, I've created a pull request (https://github.com/usocket/usocket/pull/6) some time ago. Not knowing if it was the preferred way of submitting patches. Should I append it to this list instead? Thanks in advance, Sebastian

2 2

Read Timeouts
by Mark Meyer 09 Jul '15

09 Jul '15

Hi, I'd like to discuss implementing read timeouts in usocket. I quickly looked at the docs of some implementations and found that CCL, SBCL and ClISP support it mostly effortlessly, but CMUCL does not. What's the policy for adding a feature? Does it have to be supported on all platforms? Specifically I want to get a socket stream from usocket and handle a portable usockt:read-timeout-condition when a read timeout occurs. Regards, Mark

2 2

why is usocket.asd without an in-package or package qualifiers?
by Mark H. David 16 Jun '15

16 Jun '15

I notices there's no in-package or qualifiers present in usocket.asd. So you have to, it seems, do (in-package :asdf) or similar before loading this file. Is there any good reason for this? I was thinking of fixing this and doing a pull request. Anyone against? Thanks, Mark

2 3