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

[usocket-devel] with-* style macros for sockets
by Harold Lee 26 Jan '07

26 Jan '07

Hi, I've just started using usocket, and it is very nice. The first thing I did was to write a couple of helper macros for server-side socket handling, and I thought they might be worth including in the library: (defmacro with-listener (socket-specs &rest body) "Listen for connections and clean up when done." (destructuring-bind (socket-var &rest socket-options) socket-specs (let ((var-name (gensym))) `(let* ((,var-name (socket-listen ,@socket-options)) (,socket-var ,var-name)) (unwind-protect (progn ,@body) (socket-close ,var-name)))))) (defmacro with-client-stream (socket-specs &rest body) "Work with a client socket stream and clean up when done." (destructuring-bind (stream-var listener-var &rest socket-options) socket-specs (let ((var-name (gensym))) `(let* ((,var-name (socket-accept ,listener-var ,@socket-options)) (,stream-var (socket-stream ,var-name))) (unwind-protect (progn ,@body) (socket-close ,var-name)))))) They let you easily get started listening for connections and working with connected clients (partly because all you see are the listener socket and a stream for each client). e.g. (defun handle-one-request () (with-listener (listener "127.0.0.1" 40389) (with-client-stream (stream listener) (handle-request stream)))) -Harold

2 1

[usocket-devel] Re: usocket backend/allegro.lisp
by Erik Huelsmann 23 Jan '07

23 Jan '07

> Ah, I see that this file is fixed in the subversion repository --- at > least to the extent that it loads correctly. You mean cl-irc still doesn't work for you? Yes, cl-irc works with SBCL: I have a 0.8.0 image running for some time now and haven't seen any problems. As far as documentation on the functions in allegro.lisp: for all methods and most functions, there's documentation in usocket.lisp. If that's insufficient, no problem, but I'll need directions on what's unclear so I can add it. Looking at the sources, usocket doesn't account for the case when a NIL socket is returned by Allegro. I guess usocket should return NIL when Allegro does (and cl-irc should take into account NIL is a valid return value signalling 'no socket'). Do you have any idea what could have gone wrong so that no socket was created? bye, Erik. PS: Thanks for the report. Could you CC the mailing list too? I read that more often than this mail-address. -- "Feel free" - 5 GB Mailbox, 50 FreeSMS/Monat ... Jetzt GMX ProMail testen: http://www.gmx.net/de/go/promail

3 4

[usocket-devel] Non-character element streams for sockets
by Erik Huelsmann 22 Jan '07

22 Jan '07

Hi, I'm working on a portable sockets library called usocket (see http://common-lisp.net/project/usocket/) It currently supports 9 common lisp implementations. In order to achieve true portability, I'd like to support Corman too. While I can implement most of the usocket API with the socket.lisp file (by Chris Double) I found on the 'net, it doesn't support streams of non-character element types. Could you help me with the required code/hints to support this type of streams? Thank you very much in advance! bye, Erik Huelsmann usocket initiator / main developer

1 0

[usocket-devel] usocket Scieneer support for server-side sockets
by Erik Huelsmann 19 Jan '07

19 Jan '07

Hi Douglas, I committed server side socket support to all backends but SCL. From what I saw from the parallel between CMU and SCL, I probably could code most of the required change, but, since I can't test it anyway, I'm asking you to have a look at the 3 new functions to get the SCL backend up to par. - SOCKET-LISTEN (host port &key reuseaddress backlog) - SOCKET-ACCEPT (socket) - SOCKET-CLOSE ((socket stream-server-usocket)) (method) I'll be putting :element-type support into place in the SOCKET-LISTEN function as an additional key argument. For now, that's what usocket will be supporting, seeing if all this energy pays of and people actually start using usocket (instead of recommending it to others in IRC :-) Thanks in advance! bye, Erik.

2 2

[usocket-devel] Fwd: [usocket-cvs] r174 - usocket/tags/0.2.5
by Erik Huelsmann 18 Jan '07

18 Jan '07

Because of a compilation bug (for Allegro) reported in IRC, I have released another 0.2 bugfix release. Bye, Erik. ---------- Forwarded message ---------- From: ehuelsmann(a)common-lisp.net <ehuelsmann(a)common-lisp.net> Date: Jan 19, 2007 12:48 AM Subject: [usocket-cvs] r174 - usocket/tags/0.2.5 To: usocket-cvs(a)common-lisp.net Author: ehuelsmann Date: Thu Jan 18 18:48:53 2007 New Revision: 174 Added: usocket/tags/0.2.5/ - copied from r173, usocket/branches/0.2.x/ Modified: usocket/tags/0.2.5/usocket.asd Log: Create 0.2.5 tag. Modified: usocket/tags/0.2.5/usocket.asd ============================================================================== --- usocket/branches/0.2.x/usocket.asd (original) +++ usocket/tags/0.2.5/usocket.asd Thu Jan 18 18:48:53 2007 @@ -14,7 +14,7 @@ (defsystem usocket :name "usocket" :author "Erik Enge & Erik Huelsmann" - :version "0.2.5-dev" + :version "0.2.5" :licence "MIT" :description "Universal socket library for Common Lisp" :depends-on (:split-sequence _______________________________________________ usocket-cvs mailing list usocket-cvs(a)common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/usocket-cvs

1 0

[usocket-devel] [ANNOUNCE] usocket 0.2.4
by Erik Huelsmann 18 Jan '07

18 Jan '07

Yesterday, I uploaded usocket 0.2.4. This version - fixes a problem with missing DNS hostname resolution functions in LispWorks, Allegro and OpenMCL. - fixes an OpenMCL issue where a function was called with the wrong number of arguments. - actually implements element-type support on LispWorks - fixes issue where sockets were closed without flushing first (CMUCL) Bugreports, comments and contributions very welcome! Please send notification to this list when you use usocket for your own projects (either proprietary or Open Source). bye, Erik.

1 1

[usocket-devel] Server sockets progress
by Erik Huelsmann 17 Jan '07

17 Jan '07

This week, I committed OpenMCL, LispWorks and Allegro support for server sockets to trunk. I'm hoping for people to start using / experimenting with it. Kevin, I'm especially interested in your results (if any) with OpenMCL, since I don't have Darwin to test. bye, Erik.

1 0

[usocket-devel] cl-irc now uses usocket
by Erik Huelsmann 17 Jan '07

17 Jan '07

cl-irc has switched to using usocket instead of trivial-sockets as its sockets portability layer. The switch to usocket was easy because there had been no releases depending on trivial-sockets yet and the differences in the code on the cl-irc side are small. For cl-irc this brings a whole new range of supported CL implementations. bye, Erik. PS: Do you experiment with or actually use usocket, please send a notification to this list!

1 0

[usocket-devel] Tests for server-sockets?
by Erik Huelsmann 15 Jan '07

15 Jan '07

After having committed some code which should work for several implementations, I'm now looking for a good way to implement regression testing to make sure the library stays stable and useable. Having regression tests will also speed up the implementation of the same functionality for other CL implementations. So, basically, I'm looking for a way to test server functionality in a client/server environment and I'm looking for a good way to do it. Do any of the contributers to this list have a good idea on setting it up? I'd rather not depend on a threading/multi-processing library to get the job done. Thanks in advance for any reactions! bye, Erik.

1 0

[usocket-devel] usocket SBCL server-sockets
by Erik Huelsmann 14 Jan '07

14 Jan '07

Hi! I've just committed (after brief testing) the SBCL, CMUCL and CLISP versions of server-sockets in usocket. If you'd like to test, I'd love to have your feedback! bye, Erik. PS: The implementation is lacking :element-type support and mapping of conditions; that's all scheduled, but I'd like to know this code actually works first.

1 0