Re: Out of scope? socket wrappers

Mike Abbott wrote:

>>	res.c gets pulled into libst
>>	a 'st_new_socket()' function added
>>	a 'st_bind_tcp_port(fd, port)' function added
>>	a 'st_bind_udp_port(fd, port)' function added
>>With those four functions added, a client of the libst library could
>>theorectically make use of ONLY libst calls with regards to networking.
>>    
>>
>
>I see beauty in unity too, but st was never meant to be a replacement
>for regular socket calls.  Also, from the FAQ:
>
>	Perfection is achieved not when there is nothing more to add,
>	but rather when there is nothing more to take away.
>	-- Antoine de Saint-Exupery
>  
>


I think such functions are more than 'beauty in unity'; they save real 
work by avoiding duplication of effort.





-------------------------------------------------------
This SF.net email is sponsored by: ApacheCon, November 18-21 in
Las Vegas (supported by COMDEX), the only Apache event to be
fully supported by the ASF. http://www.apachecon.com