Re: Why no socket package in the standard ?

["Yannick Duchêne (Hibou57)" <yannick_duchene@yahoo.fr>]

Le Tue, 24 May 2011 21:38:03 +0200, Yannick Duchêne (Hibou57)  
<yannick_duchene@yahoo.fr> a écrit:
>> - What should programs be able to do when communicating data
>>   along some network connection?
> Answered by the socket specification : there are raw, datagram, stream,  
> blocking and none-blocking sockets, with IPv4 or IPv6 addresses.
>
Now, was thinking raw socket should be stripped away : these are rather  
limited on Windows according to a Winsock FAQs [*], and there are good  
reasons for that; this is because a raw socket overrides OS drivers. This  
in turn can lead to security risk and efficiency troubles to not talk  
about system stability (ouch). Raw socket is useful to implement your own  
protocol over IP… which make it of a limited audience; there is no way to  
expect Ada to support such a low level topic (would be like introducing  
direct device access along with file access).

[*] I did not check for UNIcies.

-- 
Si les chats miaulent et font autant de vocalises bizarres, c’est pas pour  
les chiens.
“ c++; /* this makes c bigger but returns the old value */ ” [Anonymous]