"Jim Ursetto" <[EMAIL PROTECTED]> writes: > Although unit tcp doesn't have an explicit API for setting socket > options, it is possible to do this for server sockets. (IIRC it can't > be done at the moment for clients as that socket is not directly > exposed to the user.)
That sounds a big strange to me, the restriction on the client side. > Now, this definitely works with TCP options, but I didn't verify the > effect of setting SO_ options yet. It might not work properly because > the TCP unit calls both socket() and bind() [in ##net#bind-socket] > before you get a chance to set the socket options, and setting these > options should probably happen between those two calls. I think it would be useful to provide some identical BSD socket interfaces to C functions, such as: socket, setsockopt, bind, connect, accept, close, etc. And then TCP unit can build upon them. (I think at least Guile scheme does that.) -- William http://williamxu.net9.org _______________________________________________ Chicken-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/chicken-users
