the idea was to avoid being socket specific, as the transport layer supports things other than sockets (eg: named pipes are a work in progress here).
However, its been a while since I scrutinized that part of the code and it may make sense to use sockaddr; when I get a little bit more time for php5 hacking, I will look more closely. --Wez. > Any reason for not using struct sockaddr in favor of void? > That would align the interfaces with common socket APIs. -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
