usocket-devel

Download

usocket-devel@common-lisp.net

January 2012

3 participants
2 discussions

[usocket-devel] Unit tests failures on different lisps
by Anton Vodonosov 28 Jan '12

28 Jan '12

Hello. I am running the usocket tests (between others often-downloaded quicklisp libraries), on different lisps. The tests have different failures on different lisps. The results may be found here: http://common-lisp.net/project/cl-test-grid/pivot_ql-lib_lisp.html (the ok/fail links refer to the test logs with failure details). Some of the failures are probably bugs in tests, but other seems to be bugs in usocket itself. For example CCL on Windows: Read error between positions 195 and 295 in C:/Users/anton/quicklisp/dists/quicklisp/software/usocket-0.5.4/vendor/ccl-send.lisp. Unhandled ERROR is signaled: Foreign function not found: WIN64::|send| The variables described in README to configure the test suite - +non-existing-host+, +unused-local-port+, +common-lisp-net+ - have satisfying values (the defaults), and does not seem to be the failure cause for the failed tests. Best regards, - Anton

2 2

[usocket-devel] more convenient :nodeay option - :if-supported
by Anton Vodonosov 20 Jan '12

20 Jan '12

Hello. Today socket-connect option :nodelay if specified accepts T or NIL. And whatever value is passed, socket-connect signals the UNSUPPORTED exception on implementations where it is not possible to control the socket no-delay property. This dooms any usocket-using code which wishes to use :nodelay to be broken on implementations where it is not implemented (e.g. CLISP, CMUCL, ...). I think in most cases users would prefer "no delay if possible, otherwise just work as you can" behavior. For example drakma. On the implementations where it is possible, it will have maximum performance by specifying no-delay. But on other implementations it is desirable to work on usual socket. To support this in backward-compatible fashion I propose to introduce another value for the :nodelay option. :nodelay :if-supported. The meaning is obvious. Please see the patch attached. It is tested (by changing drakma to use :nodelay :if-supported) on all the implementations available to me: Allegro, CCL, CLISP, SBCL. Can't test on ECL and ABCL because of other obstacles (the last public release of ECL can't comile babel, and ABCL can't load cffi). Best regards, - Anton

2 1