usocket-devel February 2008

usocket-devel@common-lisp.net

3 participants
7 discussions

[usocket-devel] UDP support in usocket, ideas explained
by Erik Huelsmann 03 Oct '08

03 Oct '08

When looking at usocket.lisp, you'll find there is a datagram-usocket class commented out. I think this class (even without any additional slot definitions) should be used for UDP sockets. Then there's datagram-usocket-p, which should start returning T when the passed in object is a true descendant of DATAGRAM-USOCKET. Looking further, you'll find there are functions defined for creating stream and stream-server objects. A function like that should be created for UDP sockets. I think it's only sane to extend WAIT-FOR-INPUT to apply to UDP sockets as well as any of the currently supported sockets. The LispWorks variant of this function (for win32) is still on my laptop. I'll try to finish it up soon, so that you can all start testing it. I propose we implement recv()/recvfrom() as one function: SOCKET-RECEIVE. I think we shouldn't bother implementing recv() and recvfrom() as separate interfaces: I think we should return the recvfrom-address field as the second return value of SOCKET-RECEIVE. I also propose we implement send()/sendto() as one function: SOCKET-SEND. I think we should provide the sendto address as an optional parameter to the SOCKET-SEND function. Also, I think the function should check for connected-ness of the datagram socket. If the sendto address is specified on a connected socket AND the address specified is unequal to the connected address, the function should error. Oh. One last thing: local and peer address retrieval functions should be adapted to apply to UDP sockets as well as the currently supported stream sockets. I hope this is all a bit clear! If you have (m)any questions, please don't hesitate to ask. Bye, Erik.

2 9

[usocket-devel] Fwd: [usocket-cvs] r245 - usocket/trunk/backend
by Erik Huelsmann 23 Jul '08

23 Jul '08

Hi Douglas, I recently added some functionality in usocket and even though I think I could have copy-pasted from the CMU backend, I want to verify with you if this is true. The functions I added: - get-host-name (as you can see in the commit mail below based on copy-paste from CMU) - wait-for-input-internal which I didn't copy-paste yet. I would be especially gratefull if you could copy-paste and verify the latter for me and optionally even supply a patch. For testing of the multiplexing code, I use this 'script': (load "asdf.lisp") (asdf:oos 'asdf:load-op :usocket) (defvar sockets nil) (defparameter crlf (format nil "~C~C" #\Return #\Linefeed)) (defparameter host "mirror.w3media.nl") (defparameter offset-path "/apache") (dotimes (i 10) (let ((s (usocket:socket-connect host 80))) (format (usocket:socket-stream s) "GET http://~A~A/httpd/httpd-2.0.~A.tar.gz HTTP/1.0~%~%" host offset-path (+ 50 i)) (force-output (usocket:socket-stream s)) (push s sockets))) (let ((buffer (make-array 8192 :element-type 'character))) (loop (let ((ready (usocket:wait-for-input sockets :timeout 15))) (unless ready (sleep 1) (format t "No ready sockets!~%")) (dolist (r ready) (format t "Reading from ~A~%" r) (read-sequence buffer (usocket:socket-stream r)))))) HTH and thanks for your reaction in advance! bye, Erik. ---------- Forwarded message ---------- From: ehuelsmann(a)common-lisp.net <ehuelsmann(a)common-lisp.net> Date: May 18, 2007 12:03 AM Subject: [usocket-cvs] r245 - usocket/trunk/backend To: usocket-cvs(a)common-lisp.net Author: ehuelsmann Date: Thu May 17 18:03:55 2007 New Revision: 245 Modified: usocket/trunk/backend/scl.lisp Log: Add cl-smtp 'requirement': get-host-name (SCL backend); needs verification. Modified: usocket/trunk/backend/scl.lisp ============================================================================== --- usocket/trunk/backend/scl.lisp (original) +++ usocket/trunk/backend/scl.lisp Thu May 17 18:03:55 2007 @@ -129,3 +129,6 @@ (t (error 'ns-unknown-error :host-or-ip name :real-error errno)))))))) + +(defun get-host-name () + (unix:unix-gethostname)) _______________________________________________ usocket-cvs mailing list usocket-cvs(a)common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/usocket-cvs

4 8

[usocket-devel] Fwd: lispworks udp
by Chun Tian 26 Feb '08

26 Feb '08

Hi, usocket project More work on LispWorks UDP support has been done in these days, now I have both UDP server and client API, and send/recv message support. SVN URL is https://cl-net-snmp.svn.sourceforge.net/svnroot/cl-net-snmp/lispworks-udp P.S. still waiting for usocket UDP API:) Chun Tian (binghe) >> >> > > New message-based API and new test has been submited into SVN head, > see this demo: > > (defun udp-echo-test-3 (&optional (port 10000) (function #'identity)) > (comm:with-udp-server (server :function function :service port) > ;;; stream test > (comm:with-udp-stream (stream "localhost" port :read-timeout 1) > (let ((data "Hello, world!")) > (format stream "~A" data) > (terpri stream) ;; = "~%" or #\Newline > (force-output stream) > (format t "STREAM: Send message: ~A~%" data) > (let ((echo (read-line stream nil nil))) > (format t "STREAM: Recv message: ~A~%" echo)))) > ;; message test > (comm:with-udp-socket (socket :read-timeout 1) > (let ((data #(1 2 3 4 5 6 7 8 9 10))) > (comm:send-message socket "localhost" port data) > (format t "SOCKET: Send message: ~A~%" data) > (let ((echo (comm:receive-message socket))) > (format t "SOCKET: Recv message: ~A~%" echo)))))) > > CL-USER 101 > (udp-echo-test-3) > ;; server started > STREAM: Send message: Hello, world! > STREAM: Recv message: Hello, world! > SOCKET: Send message: #(1 2 3 4 5 6 7 8 9 10) > SOCKET: Recv message: #(1 2 3 4 5 6 7 8 9 10) > NIL > > You can choose either a MESSAGE or STREAM to do a UDP client job. I > also improved the UDP server design today with help from my friend - > a C-based network programmer, I add a RCVTIMEO into the main loop, > and we can always kill the server process successfully now. > > I think those API are stable now. > >> >> >>> I think you must be a LispWorks customer and can test the 5.1.1 >>> beta program. >> >> yes my research center employer bought the LW32 for MAc Os X >> licence. We have a Music Composition called OpenMusic that was >> written in Digitool MCL, and we have to port it to to LW because >> Digitool broke down and never came up with a Mac Intel version. >> I wrote myself an interactive improvisation system using OpenMusic >> which communicates through udp with the Max/MSP real-time >> environment : the port ws stuck since LwUdp was not available, and >> I'm not a network programmer as you guessed. >> > > I'm new to OpenMusic, it seems interest. I'll take some spare time > to look at it. Hope this porting work can be done successfully:) > >> >> Cheers and thanks again >> >> you will of course be credited in the Lispworks version of OMax (http://www.ircam.fr/equipes/repmus/OMax >> ) > > Thanks:) > >

1 0

[usocket-devel] sb-bsd-socket:protocol-unknown generates error for SBCL 1.0.14.26
by Victor Kryukov 15 Feb '08

15 Feb '08

Hello, any idea why sb-bsd-socket:protocol-unknown was added to +sbcl-condition-map+ in r302? It breaks usocket compilation on SBCL 1.0.14.26 on my system, and sbcl/contrib/sb-bsd-sockets/sockets.lisp does not define such socket condition. Regards, Victor.

2 2

[usocket-devel] test/usocket.asd
by Erik Huelsmann 10 Feb '08

10 Feb '08

Thanks for pointing that out! I've removed the offending file in revision r305. Bye, Erik.

1 0

[usocket-devel] What's the usage of USOCKET::GET-HOST-NAME in lispworks.lisp?
by Chun Tian (binghe) 01 Feb '08

01 Feb '08

Hi, I saw these definitions in lispworks.lisp: #+win32 (fli:register-module "ws2_32") (fli:define-foreign-function (get-host-name-internal "gethostname" :source) ((return-string (:reference-return (:ef-mb-string :limit 257))) (namelen :int)) :lambda-list (&aux (namelen 256) return-string) :result-type :int #+win32 :module #+win32 "ws2_32") (defun get-host-name () (multiple-value-bind (retcode name) (get-host-name-internal) (when (= 0 retcode) name))) What's the usage of GET-HOST-NAME? Can we use CL:MACHINE-INSTANCE instead? I think they have the same effect: CL-USER 4 > (machine-instance) "binghe-mac.local" CL-USER 5 > (usocket::get-host-name) "binghe-mac.local" Thanks, Chun TIAN (binghe)

2 3

[usocket-devel] LispWorks and UDP
by Chun Tian (binghe) 01 Feb '08

01 Feb '08

Hi, usocket developer Recently I wrote a LispWorks UDP support package for my pure lisp SNMP package. I use the FFI function which already in LispWorks to do a UDP job, and implement a interface which very like the exist TCP interface. You can find my code here: URL: https://cl-net-snmp.svn.sourceforge.net/svnroot/cl-net-snmp/lispworks-udp/t… Seems LispWorks, Ltd. didn't have any plan for UDP support, this package may help for usocket to implement a universal socket interface. I'll be glad for usocket to use my code, you can asdf depend it or just merge it. Regards, Chun TIAN (binghe)

2 6

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

usocket-devel February 2008