[usocket-devel] Release 0.4.0

[Chun Tian (binghe)]

Hi, Douglas

By reading SCL 1.3.8 documents, I saw the TIMEOUT keyword in  
EXT:CONNECT-TO-INET-SOCKET, so I guess just use this keyword will be  
OK to add support for TIMEOUT in USOCKET:SOCKET-CONNECT. more questions:

1. From which version of SCL, the TIMEOUT keyword be added? All SCL  
version or there's some way we can detect whether TIMEOUT can be used?  
(i.e *features*, fboundp, ...)

2. How to support DEADLINE in SCL? (I can find details from SCL doc)

3. What if we (usocket) don't split out DEADLINE from SOCKET-CONNECT  
but add a new SET-SOCKET-OPTION to set the behavior of a already  
created socket?

Regards,

Chun Tian (binghe)

> Hello Erik,
>
> Thank you for the update.
>
> The nodelay socket option can be supported in the Scieneer CL.  It  
> may also
> be useful to add this option to 'socket-accept, or perhaps split  
> this out
> into a separate function that can be used to enable or disable the  
> Nagle
> algorithm.
>
> The Scieneer CL streams support both the timeout and the deadline,  
> but also
> allow these to be reset and for the remaining time to be read which  
> is important
> for many applications.  For example a web server can reset the  
> deadline at
> the start of a new request.  So perhaps this functionality could be  
> split out
> from 'socket-connect.
>
> Regards
> Douglas Crosher
>
> ...
>> A number of smaller features (options to SOCKET-CONNECT) have also
>> been added, however, these may not be available on all
>> implementations:
>>
>> * :no-delay, which disables Naggle's algorithm
>> * :timeout, which sets a per-operation timeout on the socket
>> * :deadline, which sets a maximum life-time to the socket
> ...
>> As always, any feedback - bugs or hugs - is greatly appreciated. If
>> you use usocket, please let us know what for!
>
>
> _______________________________________________
> usocket-devel mailing list
> usocket-devel at common-lisp.net
> http://common-lisp.net/cgi-bin/mailman/listinfo/usocket-devel